Fast algorithms for symmetric motion vector difference coding mode

ABSTRACT

A method for video processing is provided. The method includes making a determination, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use a symmetric motion vector difference (SMVD) mode based on a currently selected best mode for the conversion; and performing the conversion based on the determining.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of international No. PCT/CN2020/074123, filed on Jan. 31, 2020, which claims the priority to and benefits of International Patent Application No. PCT/CN2019/074216, filed on Jan. 31, 2019, and PCT/CN2019/074433, filed on Feb. 1, 2019. All the aforementioned patent applications are hereby incorporated by reference in their entireties.

TECHNICAL FIELD

This patent document relates to video processing techniques, devices and systems.

BACKGROUND

In spite of the advances in video compression, digital video still accounts for the largest bandwidth use on the internet and other digital communication networks. As the number of connected user devices capable of receiving and displaying video increases, it is expected that the bandwidth demand for digital video usage will continue to grow.

SUMMARY

Devices, systems and methods related to digital video coding, and specifically, to motion vector predictor derivation and signaling for affine mode with adaptive motion vector resolution (AMVR) are described. The described methods may be applied to both the existing video coding standards (e.g., High Efficiency Video Coding (HEVC)) and future video coding standards or video codecs.

In one representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes determining that a conversion between a current video block of a video and a coded representation of the current video block is based on a non-affine inter AMVR mode; and performing the conversion based on the determining, and wherein the coded representation of the current video block is based on a context based coding, and wherein a context used for coding the current video block is modeled without using an affine AMVR mode information of a neighboring block during the conversion.

In another representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes determining that a conversion between a current video block of a video and a coded representation of the current video block is based on an affine adaptive motion vector resolution (affine AMVR) mode; and performing the conversion based on the determining, and wherein the coded representation of the current video block is based on a context based coding, and wherein a variable controls two probability updating speeds for a context.

In another representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes determining that a conversion between a current video block of a video and a coded representation of the current video block is based on an affine AMVR mode; and performing the conversion based on the determining, and wherein the coded representation of the current video block is based on a context based coding, and wherein a context used for coding the current video block is modeled using a coding information of a neighboring block for which an AMVR mode of both affine inter mode and normal inter mode is used during the conversion.

In another representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes determining, for a conversion between a current video block of a video and a coded representation of the current video block, a usage of multiple contexts for the conversion; and performing the conversion based on the determining, and wherein the multiple contexts are utilized for coding a syntax element indicating a coarse motion precision

In another representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes: making a determination, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use a symmetric motion vector difference (SMVD) mode based on a currently selected best mode for the conversion; and performing the conversion based on the determining.

In another representative aspect, the disclosed technology may be used to provide a method for video processing. This method includes: making a determining, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use an affine SMVD mode based on a currently selected best mode for the conversion; and performing the conversion based on the determining.

In another representative aspect, the above-described method is embodied in the form of processor-executable code and stored in a computer-readable program medium.

In yet another representative aspect, a device that is configured or operable to perform the above-described method is disclosed. The device may include a processor that is programmed to implement this method.

In yet another representative aspect, a video decoder apparatus may implement a method as described herein.

The above and other aspects and features of the disclosed technology are described in greater detail in the drawings, the description and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of constructing a merge candidate list.

FIG. 2 shows an example of positions of spatial candidates.

FIG. 3 shows an example of candidate pairs subject to a redundancy check of spatial merge candidates.

FIGS. 4A and 4B show examples of the position of a second prediction unit (PU) based on the size and shape of the current block.

FIG. 5 shows an example of motion vector scaling for temporal merge candidates.

FIG. 6 shows an example of candidate positions for temporal merge candidates.

FIG. 7 shows an example of generating a combined bi-predictive merge candidate.

FIG. 8 shows an example of constructing motion vector prediction candidates.

FIG. 9 shows an example of motion vector scaling for spatial motion vector candidates.

FIG. 10 shows an example of motion prediction using the alternative temporal motion vector prediction (ATMVP) algorithm for a coding unit (CU).

FIG. 11 shows an example of a coding unit (CU) with sub-blocks and neighboring blocks used by the spatial-temporal motion vector prediction (STMVP) algorithm.

FIGS. 12A and 12B show example snapshots of sub-block when using the overlapped block motion compensation (OBMC) algorithm.

FIG. 13 shows an example of neighboring samples used to derive parameters for the local illumination compensation (LIC) algorithm.

FIG. 14 shows an example of a simplified affine motion model.

FIG. 15 shows an example of an affine motion vector field (MVF) per sub-block.

FIG. 16 shows an example of motion vector prediction (MVP) for the AF_INTER affine motion mode.

FIGS. 17A and 17B show examples of the 4-parameter and 6-parameter affine models, respectively.

FIGS. 18A and 18B show example candidates for the AF_MERGE affine motion mode.

FIG. 19 shows an example of bilateral matching in pattern matched motion vector derivation (PMMVD) mode, which is a special merge mode based on the frame-rate up conversion (FRUC) algorithm.

FIG. 20 shows an example of template matching in the FRUC algorithm.

FIG. 21 shows an example of unilateral motion estimation in the FRUC algorithm.

FIG. 22 shows an example of an optical flow trajectory used by the bi-directional optical flow (BIO) algorithm.

FIGS. 23A and 23B show example snapshots of using of the bi-directional optical flow (BIO) algorithm without block extensions.

FIG. 24 shows an example of the decoder-side motion vector refinement (DMVR) algorithm based on bilateral template matching.

FIGS. 25A to 25F show flowcharts of example methods for video processing based on some implementations of the disclosed technology.

FIG. 26 is a block diagram of an example of a hardware platform for implementing a visual media decoding or a visual media encoding technique described in the present document.

FIG. 27 shows an example of symmetrical mode.

FIG. 28 shows another block diagram of an example of a hardware platform for implementing a video processing system described in the present document.

DETAILED DESCRIPTION

Due to the increasing demand of higher resolution video, video coding methods and techniques are ubiquitous in modern technology. Video codecs typically include an electronic circuit or software that compresses or decompresses digital video, and are continually being improved to provide higher coding efficiency. A video codec converts uncompressed video to a compressed format or vice versa. There are complex relationships between the video quality, the amount of data used to represent the video (determined by the bit rate), the complexity of the encoding and decoding algorithms, sensitivity to data losses and errors, ease of editing, random access, and end-to-end delay (latency). The compressed format usually conforms to a standard video compression specification, e.g., the High Efficiency Video Coding (HEVC) standard (also known as H.265 or MPEG-H Part 2) [1], the Versatile Video Coding standard to be finalized, or other current and/or future video coding standards.

Embodiments of the disclosed technology may be applied to existing video coding standards (e.g., HEVC, H.265) and future standards to improve compression performance. Section headings are used in the present document to improve readability of the description and do not in any way limit the discussion or the embodiments (and/or implementations) to the respective sections only.

1. Examples of Inter-Prediction in HEVC/H.265

Video coding standards have significantly improved over the years, and now provide, in part, high coding efficiency and support for higher resolutions. Recent standards such as HEVC and H.265 are based on the hybrid video coding structure wherein temporal prediction plus transform coding are utilized.

1.1 Examples of Prediction Modes

Each inter-predicted PU (prediction unit) has motion parameters for one or two reference picture lists. In some embodiments, motion parameters include a motion vector and a reference picture index. In other embodiments, the usage of one of the two reference picture lists may also be signaled using inter_pred_idc. In yet other embodiments, motion vectors may be explicitly coded as deltas relative to predictors.

When a CU is coded with skip mode, one PU is associated with the CU, and there are no significant residual coefficients, no coded motion vector delta or reference picture index. A merge mode is specified whereby the motion parameters for the current PU are obtained from neighboring PUs, including spatial and temporal candidates. The merge mode can be applied to any inter-predicted PU, not only for skip mode. The alternative to merge mode is the explicit transmission of motion parameters, where motion vector, corresponding reference picture index for each reference picture list and reference picture list usage are signaled explicitly per each PU.

When signaling indicates that one of the two reference picture lists is to be used, the PU is produced from one block of samples. This is referred to as ‘uni-prediction’. Uni-prediction is available both for P-slices and B-slices [2].

When signaling indicates that both of the reference picture lists are to be used, the PU is produced from two blocks of samples. This is referred to as ‘bi-prediction’. Bi-prediction is available for B-slices only.

1.1.1 Embodiments of Constructing Candidates for Merge Mode

When a PU is predicted using merge mode, an index pointing to an entry in the merge candidates list is parsed from the bitstream and used to retrieve the motion information. The construction of this list can be summarized according to the following sequence of steps:

-   -   Step 1: Initial candidates derivation         -   Step 1.1: Spatial candidates derivation         -   Step 1.2: Redundancy check for spatial candidates         -   Step 1.3: Temporal candidates derivation     -   Step 2: Additional candidates insertion         -   Step 2.1: Creation of bi-predictive candidates         -   Step 2.2: Insertion of zero motion candidates

FIG. 1 shows an example of constructing a merge candidate list based on the sequence of steps summarized above. For spatial merge candidate derivation, a maximum of four merge candidates are selected among candidates that are located in five different positions. For temporal merge candidate derivation, a maximum of one merge candidate is selected among two candidates. Since constant number of candidates for each PU is assumed at decoder, additional candidates are generated when the number of candidates does not reach to maximum number of merge candidate (MaxNumMergeCand) which is signalled in slice header. Since the number of candidates is constant, index of best merge candidate is encoded using truncated unary binarization (TU). If the size of CU is equal to 8, all the PUs of the current CU share a single merge candidate list, which is identical to the merge candidate list of the 2N×2N prediction unit.

1.1.2 Constructing Spatial Merge Candidates

In the derivation of spatial merge candidates, a maximum of four merge candidates are selected among candidates located in the positions depicted in FIG. 2. The order of derivation is A₁, B₁, B₀, A₀ and B₂. Position B₂ is considered only when any PU of position A₁, B₁, B₀, A₀ is not available (e.g. because it belongs to another slice or tile) or is intra coded. After candidate at position A₁ is added, the addition of the remaining candidates is subject to a redundancy check which ensures that candidates with same motion information are excluded from the list so that coding efficiency is improved.

To reduce computational complexity, not all possible candidate pairs are considered in the mentioned redundancy check. Instead only the pairs linked with an arrow in FIG. 3 are considered and a candidate is only added to the list if the corresponding candidate used for redundancy check has not the same motion information. Another source of duplicate motion information is the “second PU” associated with partitions different from 2N×2N. As an example, FIGS. 4A and 4B depict the second PU for the case of N×2N and 2N×N, respectively. When the current PU is partitioned as N×2N, candidate at position A₁ is not considered for list construction. In some embodiments, adding this candidate may lead to two prediction units having the same motion information, which is redundant to just have one PU in a coding unit. Similarly, position B₁ is not considered when the current PU is partitioned as 2N×N.

1.1.3 Constructing Temporal Merge Candidates

In this step, only one candidate is added to the list. Particularly, in the derivation of this temporal merge candidate, a scaled motion vector is derived based on co-located PU belonging to the picture which has the smallest POC difference with current picture within the given reference picture list. The reference picture list to be used for derivation of the co-located PU is explicitly signaled in the slice header.

FIG. 5 shows an example of the derivation of the scaled motion vector for a temporal merge candidate (as the dotted line), which is scaled from the motion vector of the co-located PU using the POC distances, tb and td, where tb is defined to be the POC difference between the reference picture of the current picture and the current picture and td is defined to be the POC difference between the reference picture of the co-located picture and the co-located picture. The reference picture index of temporal merge candidate is set equal to zero. For a B-slice, two motion vectors, one is for reference picture list0 and the other is for reference picture list1, are obtained and combined to make the bi-predictive merge candidate.

In the co-located PU (Y) belonging to the reference frame, the position for the temporal candidate is selected between candidates C₀ and C₁, as depicted in FIG. 6. If PU at position C₀ is not available, is intra coded, or is outside of the current CTU, position C₁ is used. Otherwise, position C₀ is used in the derivation of the temporal merge candidate.

1.1.4 Constructing Additional Types of Merge Candidates

Besides spatio-temporal merge candidates, there are two additional types of merge candidates: combined bi-predictive merge candidate and zero merge candidate. Combined bi-predictive merge candidates are generated by utilizing spatio-temporal merge candidates. Combined bi-predictive merge candidate is used for B-Slice only. The combined bi-predictive candidates are generated by combining the first reference picture list motion parameters of an initial candidate with the second reference picture list motion parameters of another. If these two tuples provide different motion hypotheses, they will form a new bi-predictive candidate.

FIG. 7 shows an example of this process, wherein two candidates in the original list (710, on the left), which have mvL0 and refIdxL0 or mvL1 and refIdxL1, are used to create a combined bi-predictive merge candidate added to the final list (720, on the right).

Zero motion candidates are inserted to fill the remaining entries in the merge candidates list and therefore hit the MaxNumMergeCand capacity. These candidates have zero spatial displacement and a reference picture index which starts from zero and increases every time a new zero motion candidate is added to the list. The number of reference frames used by these candidates is one and two for uni- and bi-directional prediction, respectively. In some embodiments, no redundancy check is performed on these candidates.

1.1.5 Examples of Motion Estimation Regions for Parallel Processing

To speed up the encoding process, motion estimation can be performed in parallel whereby the motion vectors for all prediction units inside a given region are derived simultaneously. The derivation of merge candidates from spatial neighborhood may interfere with parallel processing as one prediction unit cannot derive the motion parameters from an adjacent PU until its associated motion estimation is completed. To mitigate the trade-off between coding efficiency and processing latency, a motion estimation region (MER) may be defined. The size of the MER may be signaled in the picture parameter set (PPS) using the “log 2_parallel_merge_level _minus2” syntax element. When a MER is defined, merge candidates falling in the same region are marked as unavailable and therefore not considered in the list construction.

1.2 Embodiments of Advanced Motion Vector Prediction (AMVP)

AMVP exploits spatio-temporal correlation of motion vector with neighboring PUs, which is used for explicit transmission of motion parameters. It constructs a motion vector candidate list by firstly checking availability of left, above temporally neighboring PU positions, removing redundant candidates and adding zero vector to make the candidate list to be constant length. Then, the encoder can select the best predictor from the candidate list and transmit the corresponding index indicating the chosen candidate. Similarly with merge index signaling, the index of the best motion vector candidate is encoded using truncated unary. The maximum value to be encoded in this case is 2 (see FIG. 8). In the following sections, details about derivation process of motion vector prediction candidate are provided.

1.2.1 Examples of Constructing Motion Vector Prediction Candidates

FIG. 8 summarizes derivation process for motion vector prediction candidate, and may be implemented for each reference picture list with refidx as an input.

In motion vector prediction, two types of motion vector candidates are considered: spatial motion vector candidate and temporal motion vector candidate. For spatial motion vector candidate derivation, two motion vector candidates are eventually derived based on motion vectors of each PU located in five different positions as previously shown in FIG. 2.

For temporal motion vector candidate derivation, one motion vector candidate is selected from two candidates, which are derived based on two different co-located positions. After the first list of spatio-temporal candidates is made, duplicated motion vector candidates in the list are removed. If the number of potential candidates is larger than two, motion vector candidates whose reference picture index within the associated reference picture list is larger than 1 are removed from the list. If the number of spatio-temporal motion vector candidates is smaller than two, additional zero motion vector candidates is added to the list.

1.2.2 Constructing Spatial Motion Vector Candidates

In the derivation of spatial motion vector candidates, a maximum of two candidates are considered among five potential candidates, which are derived from PUs located in positions as previously shown in FIG. 2, those positions being the same as those of motion merge. The order of derivation for the left side of the current PU is defined as A₀, A₁, and scaled A₀, scaled A₁. The order of derivation for the above side of the current PU is defined as B₀, B₁, B₂, scaled B₀, scaled B₁, scaled B₂. For each side there are therefore four cases that can be used as motion vector candidate, with two cases not required to use spatial scaling, and two cases where spatial scaling is used. The four different cases are summarized as follows:

-   -   No spatial scaling         -   (1) Same reference picture list, and same reference picture             index (same POC)         -   (2) Different reference picture list, but same reference             picture (same POC)     -   Spatial scaling         -   (3) Same reference picture list, but different reference             picture (different POC)         -   (4) Different reference picture list, and different             reference picture (different POC)

The no-spatial-scaling cases are checked first followed by the cases that allow spatial scaling. Spatial scaling is considered when the POC is different between the reference picture of the neighbouring PU and that of the current PU regardless of reference picture list. If all PUs of left candidates are not available or are intra coded, scaling for the above motion vector is allowed to help parallel derivation of left and above MV candidates. Otherwise, spatial scaling is not allowed for the above motion vector.

As shown in the example in FIG. 9, for the spatial scaling case, the motion vector of the neighbouring PU is scaled in a similar manner as for temporal scaling. One difference is that the reference picture list and index of current PU is given as input; the actual scaling process is the same as that of temporal scaling.

1.2.3 Constructing Temporal Motion Vector Candidates

Apart from the reference picture index derivation, all processes for the derivation of temporal merge candidates are the same as for the derivation of spatial motion vector candidates (as shown in the example in FIG. 6). In some embodiments, the reference picture index is signaled to the decoder.

2. Example of Inter Prediction Methods in Joint Exploration Model (JEM)

In some embodiments, future video coding technologies are explored using a reference software known as the Joint Exploration Model (JEM) [3][4]. In JEM, sub-block based prediction is adopted in several coding tools, such as affine prediction, alternative temporal motion vector prediction (ATMVP), spatial-temporal motion vector prediction (STMVP), bi-directional optical flow (BIO), Frame-Rate Up Conversion (FRUC), Locally Adaptive Motion Vector Resolution (LAMVR), Overlapped Block Motion Compensation (OBMC), Local Illumination Compensation (LIC), and Decoder-side Motion Vector Refinement (DMVR).

2.1 Examples of Sub-CU Based Motion Vector Prediction

In the JEM with quadtrees plus binary trees (QTBT), each CU can have at most one set of motion parameters for each prediction direction. In some embodiments, two sub-CU level motion vector prediction methods are considered in the encoder by splitting a large CU into sub-CUs and deriving motion information for all the sub-CUs of the large CU. Alternative temporal motion vector prediction (ATMVP) method allows each CU to fetch multiple sets of motion information from multiple blocks smaller than the current CU in the collocated reference picture. In spatial-temporal motion vector prediction (STMVP) method motion vectors of the sub-CUs are derived recursively by using the temporal motion vector predictor and spatial neighbouring motion vector. In some embodiments, and to preserve more accurate motion field for sub-CU motion prediction, the motion compression for the reference frames may be disabled.

2.1.1 Examples of Alternative Temporal Motion Vector Prediction (ATMVP)

In the ATMVP method, the temporal motion vector prediction (TMVP) method is modified by fetching multiple sets of motion information (including motion vectors and reference indices) from blocks smaller than the current CU.

FIG. 10 shows an example of ATMVP motion prediction process for a CU 1000. The ATMVP method predicts the motion vectors of the sub-CUs 1001 within a CU 1000 in two steps. The first step is to identify the corresponding block 1051 in a reference picture 1050 with a temporal vector. The reference picture 1050 is also referred to as the motion source picture. The second step is to split the current CU 1000 into sub-CUs 1001 and obtain the motion vectors as well as the reference indices of each sub-CU from the block corresponding to each sub-CU.

In the first step, a reference picture 1050 and the corresponding block is determined by the motion information of the spatial neighboring blocks of the current CU 1000. To avoid the repetitive scanning process of neighboring blocks, the first merge candidate in the merge candidate list of the current CU 1000 is used. The first available motion vector as well as its associated reference index are set to be the temporal vector and the index to the motion source picture. This way, the corresponding block may be more accurately identified, compared with TMVP, wherein the corresponding block (sometimes called collocated block) is always in a bottom-right or center position relative to the current CU.

In the second step, a corresponding block of the sub-CU 1051 is identified by the temporal vector in the motion source picture 1050, by adding to the coordinate of the current CU the temporal vector. For each sub-CU, the motion information of its corresponding block (e.g., the smallest motion grid that covers the center sample) is used to derive the motion information for the sub-CU. After the motion information of a corresponding N×N block is identified, it is converted to the motion vectors and reference indices of the current sub-CU, in the same way as TMVP of HEVC, wherein motion scaling and other procedures apply. For example, the decoder checks whether the low-delay condition (e.g. the POCs of all reference pictures of the current picture are smaller than the POC of the current picture) is fulfilled and possibly uses motion vector MVx (e.g., the motion vector corresponding to reference picture list X) to predict motion vector MVy (e.g., with X being equal to 0 or 1 and Y being equal to 1−X) for each sub-CU.

2.1.2 Examples of Spatial-Temporal Motion Vector Prediction (STMVP)

In the STMVP method, the motion vectors of the sub-CUs are derived recursively, following raster scan order. FIG. 11 shows an example of one CU with four sub-blocks and neighboring blocks. Consider an 8×8 CU 1100 that includes four 4×4 sub-CUs A (1101), B (1102), C (1103), and D (1104). The neighboring 4×4 blocks in the current frame are labelled as a (1111), b (1112), c (1113), and d (1114).

The motion derivation for sub-CU A starts by identifying its two spatial neighbors. The first neighbor is the N×N block above sub-CU A 1101 (block c 1113). If this block c (1113) is not available or is intra coded the other N×N blocks above sub-CU A (1101) are checked (from left to right, starting at block c 1113). The second neighbor is a block to the left of the sub-CU A 1101 (block b 1112). If block b (1112) is not available or is intra coded other blocks to the left of sub-CU A 1101 are checked (from top to bottom, staring at block b 1112). The motion information obtained from the neighboring blocks for each list is scaled to the first reference frame for a given list. Next, temporal motion vector predictor (TMVP) of sub-block A 1101 is derived by following the same procedure of TMVP derivation as specified in HEVC. The motion information of the collocated block at block D 1104 is fetched and scaled accordingly. Finally, after retrieving and scaling the motion information, all available motion vectors are averaged separately for each reference list. The averaged motion vector is assigned as the motion vector of the current sub-CU.

2.1.3 Examples of Sub-CU Motion Prediction Mode Signaling

In some embodiments, the sub-CU modes are enabled as additional merge candidates and there is no additional syntax element required to signal the modes. Two additional merge candidates are added to merge candidates list of each CU to represent the ATMVP mode and STMVP mode. In other embodiments, up to seven merge candidates may be used, if the sequence parameter set indicates that ATMVP and STMVP are enabled. The encoding logic of the additional merge candidates is the same as for the merge candidates in the HM, which means, for each CU in P or B slice, two more RD checks may be needed for the two additional merge candidates. In some embodiments, e.g., JEM, all bins of the merge index are context coded by CABAC (Context-based Adaptive Binary Arithmetic Coding). In other embodiments, e.g., HEVC, only the first bin is context coded and the remaining bins are context by-pass coded.

2.2 Examples of Adaptive Motion Vector Difference Resolution

In some embodiments, motion vector differences (MVDs) (between the motion vector and predicted motion vector of a PU) are signalled in units of quarter luma samples when use_integer _mv _flag is equal to 0 in the slice header. In the JEM, a locally adaptive motion vector resolution (LAMVR) is introduced. In the JEM, MVD can be coded in units of quarter luma samples, integer luma samples or four luma samples. The MVD resolution is controlled at the coding unit (CU) level, and MVD resolution flags are conditionally signalled for each CU that has at least one non-zero MVD components.

For a CU that has at least one non-zero MVD components, a first flag is signalled to indicate whether quarter luma sample MV precision is used in the CU. When the first flag (equal to 1) indicates that quarter luma sample MV precision is not used, another flag is signalled to indicate whether integer luma sample MV precision or four luma sample MV precision is used.

When the first MVD resolution flag of a CU is zero, or not coded for a CU (meaning all MVDs in the CU are zero), the quarter luma sample MV resolution is used for the CU. When a CU uses integer-luma sample MV precision or four-luma-sample MV precision, the MVPs in the AMVP candidate list for the CU are rounded to the corresponding precision.

In the encoder, CU-level RD checks are used to determine which MVD resolution is to be used for a CU. That is, the CU-level RD check is performed three times for each MVD resolution. To accelerate encoder speed, the following encoding schemes are applied in the JEM:

-   -   During RD check of a CU with normal quarter luma sample MVD         resolution, the motion information of the current CU (integer         luma sample accuracy) is stored. The stored motion information         (after rounding) is used as the starting point for further small         range motion vector refinement during the RD check for the same         CU with integer luma sample and 4 luma sample MVD resolution so         that the time-consuming motion estimation process is not         duplicated three times.     -   RD check of a CU with 4 luma sample MVD resolution is         conditionally invoked. For a CU, when RD cost integer luma         sample MVD resolution is much larger than that of quarter luma         sample MVD resolution, the RD check of 4 luma sample MVD         resolution for the CU is skipped.

2.3 Examples of Higher Motion Vector Storage Accuracy

In HEVC, motion vector accuracy is one-quarter pel (one-quarter luma sample and one-eighth chroma sample for 4:2:0 video). In the JEM, the accuracy for the internal motion vector storage and the merge candidate increases to 1/16 pel. The higher motion vector accuracy ( 1/16 pel) is used in motion compensation inter prediction for the CU coded with skip/merge mode. For the CU coded with normal AMVP mode, either the integer-pel or quarter-pel motion is used.

SHVC upsampling interpolation filters, which have same filter length and normalization factor as HEVC motion compensation interpolation filters, are used as motion compensation interpolation filters for the additional fractional pel positions. The chroma component motion vector accuracy is 1/32 sample in the JEM, the additional interpolation filters of 1/32 pel fractional positions are derived by using the average of the filters of the two neighbouring 1/16 pel fractional positions.

2.4 Examples of Overlapped Block Motion Compensation (OBMC)

In the JEM, OBMC can be switched on and off using syntax at the CU level. When OBMC is used in the JEM, the OBMC is performed for all motion compensation (MC) block boundaries except the right and bottom boundaries of a CU. Moreover, it is applied for both the luma and chroma components. In the JEM, an MC block corresponds to a coding block. When a CU is coded with sub-CU mode (includes sub-CU merge, affine and FRUC mode), each sub-block of the CU is a MC block. To process CU boundaries in a uniform fashion, OBMC is performed at sub-block level for all MC block boundaries, where sub-block size is set equal to 4×4, as shown in FIGS. 12A and 12B.

FIG. 12A shows sub-blocks at the CU/PU boundary, and the hatched sub-blocks are where OBMC applies. Similarly, FIG. 12B shows the sub-Pus in ATMVP mode.

When OBMC applies to the current sub-block, besides current motion vectors, motion vectors of four connected neighboring sub-blocks, if available and are not identical to the current motion vector, are also used to derive prediction block for the current sub-block. These multiple prediction blocks based on multiple motion vectors are combined to generate the final prediction signal of the current sub-block.

Prediction block based on motion vectors of a neighboring sub-block is denoted as PN, with N indicating an index for the neighboring above, below, left and right sub-blocks and prediction block based on motion vectors of the current sub-block is denoted as PC. When PN is based on the motion information of a neighboring sub-block that contains the same motion information to the current sub-block, the OBMC is not performed from PN. Otherwise, every sample of PN is added to the same sample in PC, i.e., four rows/columns of PN are added to PC. The weighting factors {¼, ⅛, 1/16, 1/32} are used for PN and the weighting factors {¾, ⅞, 15/16, 31/32} are used for PC. The exception are small MC blocks, (i.e., when height or width of the coding block is equal to 4 or a CU is coded with sub-CU mode), for which only two rows/columns of PN are added to PC. In this case weighting factors {¼, ⅛} are used for PN and weighting factors {¾, ⅞} are used for PC. For PN generated based on motion vectors of vertically (horizontally) neighboring sub-block, samples in the same row (column) of PN are added to PC with a same weighting factor.

In the JEM, for a CU with size less than or equal to 256 luma samples, a CU level flag is signaled to indicate whether OBMC is applied or not for the current CU. For the CUs with size larger than 256 luma samples or not coded with AMVP mode, OBMC is applied by default. At the encoder, when OBMC is applied for a CU, its impact is taken into account during the motion estimation stage. The prediction signal formed by OBMC using motion information of the top neighboring block and the left neighboring block is used to compensate the top and left boundaries of the original signal of the current CU, and then the normal motion estimation process is applied.

2.5 Examples of Local Illumination Compensation (LIC)

LIC is based on a linear model for illumination changes, using a scaling factor a and an offset b. And it is enabled or disabled adaptively for each inter-mode coded coding unit (CU).

When LIC applies for a CU, a least square error method is employed to derive the parameters a and b by using the neighboring samples of the current CU and their corresponding reference samples. FIG. 13 shows an example of neighboring samples used to derive parameters of the IC algorithm. Specifically, and as shown in FIG. 13, the subsampled (2:1 subsampling) neighbouring samples of the CU and the corresponding samples (identified by motion information of the current CU or sub-CU) in the reference picture are used. The IC parameters are derived and applied for each prediction direction separately.

When a CU is coded with merge mode, the LIC flag is copied from neighboring blocks, in a way similar to motion information copy in merge mode; otherwise, an LIC flag is signaled for the CU to indicate whether LIC applies or not.

When LIC is enabled for a picture, an additional CU level RD check is needed to determine whether LIC is applied or not for a CU. When LIC is enabled for a CU, the mean-removed sum of absolute difference (MR-SAD) and mean-removed sum of absolute Hadamard-transformed difference (MR-SATD) are used, instead of SAD and SATD, for integer pel motion search and fractional pel motion search, respectively.

To reduce the encoding complexity, the following encoding scheme is applied in the JEM:

-   -   LIC is disabled for the entire picture when there is no obvious         illumination change between a current picture and its reference         pictures. To identify this situation, histograms of a current         picture and every reference picture of the current picture are         calculated at the encoder. If the histogram difference between         the current picture and every reference picture of the current         picture is smaller than a given threshold, LIC is disabled for         the current picture; otherwise, LIC is enabled for the current         picture.

2.6 Examples of Affine Motion Compensation Prediction

In HEVC, only a translation motion model is applied for motion compensation prediction (MCP). However, the camera and objects may have many kinds of motion, e.g. zoom in/out, rotation, perspective motions, and/or other irregular motions. JEM, on the other hand, applies a simplified affine transform motion compensation prediction. FIG. 14 shows an example of an affine motion field of a block 1400 described by two control point motion vectors V₀ and V₁. The motion vector field (MVF) of the block 1400 can be described by the following equation:

$\begin{matrix} \left\{ \begin{matrix} {v_{x} = {{\frac{\left( {v_{1x} - v_{0x}} \right)}{w}x} - {\frac{\left( {v_{1y} - v_{0_{y}}} \right)}{w}y} + v_{0x}}} \\ {v_{y} = {{\frac{\left( {v_{1y} - v_{0y}} \right)}{w}x} + {\frac{\left( {v_{1x} - v_{0_{x}}} \right)}{w}y} + v_{0y}}} \end{matrix} \right. & {{Eq}.\mspace{14mu}(1)} \end{matrix}$

As shown in FIG. 14, (v_(0x), v_(0y)) is motion vector of the top-left corner control point, and (v_(1x), v_(1y)) is motion vector of the top-right corner control point. To simplify the motion compensation prediction, sub-block based affine transform prediction can be applied. The sub-block size MxN is derived as follows:

$\begin{matrix} \left\{ \begin{matrix} {M = {{clip}\ 3\ \left( {4,w,\frac{w \times {MvPre}}{\max\left( {{{abs}\left( {v_{1x} - v_{0x}} \right)},{{abs}\left( {v_{1y} - v_{0y}} \right)}} \right)}} \right)}} \\ {N = {{clip}\ 3\ \left( {4,h,\frac{h \times {MvPre}}{\max\left( {{{abs}\left( {v_{2x} - v_{0x}} \right)},{{abs}\left( {v_{2y} - v_{0y}} \right)}} \right)}} \right)}} \end{matrix} \right. & {{Eq}.\mspace{14mu}(2)} \end{matrix}$

Here, MvPre is the motion vector fraction accuracy (e.g., 1/16 in JEM). (v_(2x), v_(2y)) is motion vector of the bottom-left control point, calculated according to Eq. (1). M and N can be adjusted downward if necessary to make it a divisor of w and h, respectively.

FIG. 15 shows an example of affine MVF per sub-block for a block 1500. To derive motion vector of each M×N sub-block, the motion vector of the center sample of each sub-block can be calculated according to Eq. (1), and rounded to the motion vector fraction accuracy (e.g., 1/16 in JEM). Then the motion compensation interpolation filters can be applied to generate the prediction of each sub-block with derived motion vector. After the MCP, the high accuracy motion vector of each sub-block is rounded and saved as the same accuracy as the normal motion vector.

2.6.1 Embodiments of the AF_INTER Mode

In the JEM, there are two affine motion modes: AF_INTER mode and AF_MERGE mode. For CUs with both width and height larger than 8, AF_INTER mode can be applied. An affine flag in CU level is signaled in the bitstream to indicate whether AF_INTER mode is used. In the AF_INTER mode, a candidate list with motion vector pair {(v₀, v₁)|v₀={v_(A), v_(B), v_(C)}, v₁={v_(D), v_(E)}} is constructed using the neighboring blocks.

FIG. 16 shows an example of motion vector prediction (MVP) for a block 1600 in the AF_INTER mode. As shown in FIG. 16, v₀ is selected from the motion vectors of the sub-block A, B, or C. The motion vectors from the neighboring blocks can be scaled according to the reference list. The motion vectors can also be scaled according to the relationship among the Picture Order Count (POC) of the reference for the neighboring block, the POC of the reference for the current CU, and the POC of the current CU. The approach to select v₁ from the neighboring sub-block D and E is similar. If the number of candidate list is smaller than 2, the list is padded by the motion vector pair composed by duplicating each of the AMVP candidates. When the candidate list is larger than 2, the candidates can be firstly sorted according to the neighboring motion vectors (e.g., based on the similarity of the two motion vectors in a pair candidate). In some implementations, the first two candidates are kept. In some embodiments, a Rate Distortion (RD) cost check is used to determine which motion vector pair candidate is selected as the control point motion vector prediction (CPMVP) of the current CU. An index indicating the position of the CPMVP in the candidate list can be signaled in the bitstream. After the CPMVP of the current affine CU is determined, affine motion estimation is applied and the control point motion vector (CPMV) is found. Then the difference of the CPMV and the CPMVP is signaled in the bitstream.

In AF_INTER mode, when 4/6 parameter affine mode is used, ⅔ control points are required, and therefore ⅔ MVD needs to be coded for these control points, as shown in FIG. 17. In an existing implementation [5], the MV may be derived as follows, e.g., it predicts mvd₁ and mvd₂ from mvd₀.

mv ₀ =mv ₀ +mvd ₀

mv ₁ =mv ₁ +mvd ₁ +mvd ₁

mv ₂ =mv ₂ +mvd ₂ +mvd ₀

Herein, mv _(i), mvd_(i) and mv₁ are the predicted motion vector, motion vector difference and motion vector of the top-left pixel (i=0), top-right pixel (i=1) or left-bottom pixel (i=2) respectively, as shown in FIG. 18B. In some embodiments, the addition of two motion vectors (e.g., mvA(xA, yA) and mvB(xB, yB)) is equal to summation of two components separately. For example, newMV=mvA+mvB implies that the two components of newMV are set to (xA+xB) and (yA+yB), respectively.

2.6.2 Examples of Fast Affine ME Algorithms in AF_INTER Mode

In some embodiments of the affine mode, MV of 2 or 3 control points needs to be determined jointly. Directly searching the multiple MVs jointly is computationally complex. In an example, a fast affine ME algorithm [6] is proposed and is adopted into VTM/BMS.

For example, the fast affine ME algorithm is described for the 4-parameter affine model, and the idea can be extended to 6-parameter affine model:

$\begin{matrix} \left\{ \begin{matrix} {x^{\prime} = {{ax} + {by} + c}} \\ {y^{\prime} = {{- {bx}} + {ay} + d}} \end{matrix} \right. & {{Eq}.\mspace{14mu}(3)} \\ \left\{ \begin{matrix} {{mv_{({x,y})}^{h}} = {{x^{\prime} - x} = {{\left( {a - 1} \right)x} + {by} + c}}} \\ {{mv_{({x,y})}^{v}} = {{y^{\prime} - y} = {{{- b}x} + {\left( {a - 1} \right)y} + d}}} \end{matrix} \right. & {{Eq}.\mspace{14mu}(4)} \end{matrix}$

Replacing (a-1) with a′ enables the motion vectors to be rewritten as:

$\begin{matrix} \left\{ \begin{matrix} {{mv_{({x,y})}^{h}} = {{x^{\prime} - x} = {{a^{\prime}x} + {by} + c}}} \\ {{mv_{({x,y})}^{v}} = {{y^{\prime} - y} = {{{- b}x} + {a^{\prime}y} + d}}} \end{matrix} \right. & {{Eq}.\mspace{14mu}(5)} \end{matrix}$

If it is assumed that the motion vectors of the two controls points (0, 0) and (0, w) are known, from Equation (5) the affine parameters may be derived as:

$\begin{matrix} {\left\{ \begin{matrix} {c = {mv_{({0,0})}^{h}}} \\ {d = {mv_{({0,0})}^{v}}} \end{matrix} \right..} & {{Eq}.\mspace{14mu}(6)} \end{matrix}$

The motion vectors can be rewritten in vector form as:

MV(p)=A(P)*MV _(C) ^(T)  Eq. (7)

Herein, P=(x, y) is the pixel position,

$\begin{matrix} {{{A(P)} = \begin{bmatrix} 1 & x & 0 & y \\ 0 & y & 1 & {- x} \end{bmatrix}},{and}} & {{Eq}.\mspace{14mu}(8)} \\ {{MV_{C}} = {\left\lbrack {mv_{({0,0})}^{h}\ a\ mv_{({0,0})}^{v}b} \right\rbrack.}} & {{Eq}.\mspace{14mu}(9)} \end{matrix}$

In some embodiments, and at the encoder, the MVD of AF_INTER may be derived iteratively. Denote MV^(i)(P) as the MV derived in the ith iteration for position P and denote dMV_(C) ^(i) as the delta updated for MV_(C) in the ith iteration. Then in the (i+1)th iteration,

$\begin{matrix} \begin{matrix} {{M{V^{i + 1}(P)}} = {{A(P)}*\left( {\left( {MV_{C}^{i}} \right)^{T} + \left( {dMV_{C}^{i}} \right)^{T}} \right)}} \\ {= {{{A(P)}*\left( {MV_{C}^{i}} \right)^{T}} + {{A(P)}*\left( {dMV_{C}^{i}} \right)^{T}}}} \\ {= {{M{V^{i}(P)}} + {{A(P)}*{\left( {dMV_{C}^{i}} \right)^{T}.}}}} \end{matrix} & {{Eq}.\mspace{14mu}(10)} \end{matrix}$

Denote Pic_(ref) as the reference picture and denote Pic_(cur) as the current picture and denote Q=P+MV^(i)(P). If the MSE is used as the matching criterion, then the function that needs to be minimized may be written as:

min Σ_(P)(Pic _(cur)(P)−Pic _(ref)(P+MV ^(i+1)(P)))²=

min Σ_(P)(Pic _(cur)(P)−Pic _(ref)(Q+A(P)*(dMV _(C) ^(i))^(T)))²  Eq. (11)

If it is assumed that (dMV_(C) ^(i))T small enough, Pic_(ref) (Q+A(P)*(dMV_(C) ^(i))^(T)) may be rewritten, as an approximation based on a 1-st order Taylor expansion, as:

Pic _(ref)(Q+A(P)*(dMV _(C) ^(i))^(T))≈Pic _(ref)(Q)+Pic _(ref)′(Q)*A(P)*(dMV _(C) ^(i))^(T)  (12)

Herein,

${{Pic}_{ref}^{\prime}(Q)} = {\left\lbrack {\frac{dPi{c_{ref}(Q)}}{dx}\frac{dPi{c_{ref}(Q)}}{dy}} \right\rbrack.}$

If the notation E^(i+1)(P)=Pic_(cur)(P)−

Pic_(ref)(Q) is adopted, then:

Min Σ_(P)(Pic _(cur)(P)−Pic _(ref)(Q)Pic _(ref)′(Q)*A(P)*(dMV _(C) ^(i))^(T))²=

min Σ_(P)(E ^(i+1)(P)−Pic _(ref)′(Q)*A(P)*(dMV _(C) ^(i))^(T))²  Eq. (13)

The term dMV_(C) ^(i) may be derived by setting the derivative of the error function to zero, and then computing delta MV of the control points (0, 0) and (0, w) according to A(P)*(dMV_(C) ^(i))^(T), as follows:

dMV ^(h) _((0,0)) =dMV _(C) ^(i)[0]  Eq. (14)

dMV ^(h) _((0,w)) =dMV _(C) ^(i)[1]*w+dMV _(C) ^(i)[2]  Eq. (15)

dMV ^(v) _((0,0)) =dMV _(C) ^(i)[2]  Eq. (16)

dMV ^(v) _((0,w)) =dMV _(C) ^(i)[3]*w+dMV _(C) ^(i)[2]  Eq. (17)

In some embodiments, this MVD derivation process may be iterated n times, and the final MVD may be calculated as follows:

fdMV ^(h) _((0,0))=Σ_(i=0) ^(n−1) dMV _(C) ^(i)[0]  Eq. (18)

fdMV ^(h) _((0,w))=Σ_(i=0) ^(n−1) dMV _(C) ^(i)[1]*w+Σ _(i=0) ^(n−1) dMV _(C) ^(i)[0]  Eq.(19)

fdMV ^(v) _((0,0))=Σ_(i=0) ^(n−1) dMV _(C) ^(i)[2]  Eq. (20)

fdMV ^(v) _((0,w))=Σ_(i=0) ^(n−1) −dMV _(C) ^(i)[3]*w+Σ _(i=0) ^(n−1) dMV _(C) ^(i)[2]  Eq.(21)

In the aforementioned implementation [5], predicting delta MV of control point (0, w), denoted by mvd₁ from delta MV of control point (0, 0), denoted by mvd₀, results in only (Σ_(i=0) ^(n−1) dMV_(C) ^(i)[1]*w,−Σ_(i=0) ^(n−1)−dMV_(C) ^(i)[3]*w) being encoded for mvd₁.

2.6.3 Embodiments of the AF_MERGE Mode

When a CU is applied in AF_MERGE mode, it gets the first block coded with an affine mode from the valid neighboring reconstructed blocks. FIG. 18A shows an example of the selection order of candidate blocks for a current CU 1800. As shown in FIG. 18A, the selection order can be from left (1801), above (1802), above right (1803), left bottom (1804) to above left (1805) of the current CU 1800. FIG. 18B shows another example of candidate blocks for a current CU 1800 in the AF_MERGE mode. If the neighboring left bottom block 1801 is coded in affine mode, as shown in FIG. 18B, the motion vectors v₂, v₃ and v₄ of the top left corner, above right corner, and left bottom corner of the CU containing the sub-block 1801 are derived. The motion vector v₀ of the top left corner on the current CU 1800 is calculated based on v₂, v₃ and v₄. The motion vector v₁ of the above right of the current CU can be calculated accordingly.

After the CPMV of the current CU v₀ and v₁ are computed according to the affine motion model in Eq. (1), the MVF of the current CU can be generated. In order to identify whether the current CU is coded with AF_MERGE mode, an affine flag can be signaled in the bitstream when there is at least one neighboring block is coded in affine mode.

2.7 Examples of Pattern Matched Motion Vector Derivation (PMMVD)

The PMMVD mode is a special merge mode based on the Frame-Rate Up Conversion (FRUC) method. With this mode, motion information of a block is not signaled but derived at decoder side.

A FRUC flag can be signaled for a CU when its merge flag is true. When the FRUC flag is false, a merge index can be signaled and the regular merge mode is used. When the FRUC flag is true, an additional FRUC mode flag can be signaled to indicate which method (e.g., bilateral matching or template matching) is to be used to derive motion information for the block.

At the encoder side, the decision on whether using FRUC merge mode for a CU is based on RD cost selection as done for normal merge candidate. For example, multiple matching modes (e.g., bilateral matching and template matching) are checked for a CU by using RD cost selection. The one leading to the minimal cost is further compared to other CU modes. If a FRUC matching mode is the most efficient one, FRUC flag is set to true for the CU and the related matching mode is used.

Typically, motion derivation process in FRUC merge mode has two steps: a CU-level motion search is first performed, then followed by a Sub-CU level motion refinement. At CU level, an initial motion vector is derived for the whole CU based on bilateral matching or template matching. First, a list of MV candidates is generated and the candidate that leads to the minimum matching cost is selected as the starting point for further CU level refinement. Then a local search based on bilateral matching or template matching around the starting point is performed. The MV results in the minimum matching cost is taken as the MV for the whole CU. Subsequently, the motion information is further refined at sub-CU level with the derived CU motion vectors as the starting points.

For example, the following derivation process is performed for a W×H CU motion information derivation. At the first stage, MV for the whole W×H CU is derived. At the second stage, the CU is further split into M×M sub-CUs. The value of M is calculated as in Eq. (3), D is a predefined splitting depth which is set to 3 by default in the JEM. Then the MV for each sub-CU is derived.

$\begin{matrix} {M = {\max\left\{ {4,{\min\left\{ {\frac{M}{2^{D}},\frac{N}{2^{D}}} \right\}}} \right\}}} & {{Eq}.\mspace{14mu}(3)} \end{matrix}$

FIG. 19 shows an example of bilateral matching used in the Frame-Rate Up Conversion (FRUC) method. The bilateral matching is used to derive motion information of the current CU by finding the closest match between two blocks along the motion trajectory of the current CU (1900) in two different reference pictures (1910, 1911). Under the assumption of continuous motion trajectory, the motion vectors MV0 (1901) and MV1 (1902) pointing to the two reference blocks are proportional to the temporal distances, e.g., TD0 (1903) and TD1 (1904), between the current picture and the two reference pictures. In some embodiments, when the current picture 1900 is temporally between the two reference pictures (1910, 1911) and the temporal distance from the current picture to the two reference pictures is the same, the bilateral matching becomes mirror based bi-directional MV.

FIG. 20 shows an example of template matching used in the Frame-Rate Up Conversion (FRUC) method. Template matching can be used to derive motion information of the current CU 2000 by finding the closest match between a template (e.g., top and/or left neighboring blocks of the current CU) in the current picture and a block (e.g., same size to the template) in a reference picture 2010. Except the aforementioned FRUC merge mode, the template matching can also be applied to AMVP mode. In both JEM and HEVC, AMVP has two candidates. With the template matching method, a new candidate can be derived. If the newly derived candidate by template matching is different to the first existing AMVP candidate, it is inserted at the very beginning of the AMVP candidate list and then the list size is set to two (e.g., by removing the second existing AMVP candidate). When applied to AMVP mode, only CU level search is applied.

The MV candidate set at CU level can include the following: (1) original AMVP candidates if the current CU is in AMVP mode, (2) all merge candidates, (3) several MVs in the interpolated MV field (described later), and top and left neighboring motion vectors.

When using bilateral matching, each valid MV of a merge candidate can be used as an input to generate a MV pair with the assumption of bilateral matching. For example, one valid MV of a merge candidate is (MVa, ref_(a)) at reference list A. Then the reference picture ref_(b) of its paired bilateral MV is found in the other reference list B so that ref_(a) and ref_(b) are temporally at different sides of the current picture. If such a ref_(b) is not available in reference list B, ref_(b) is determined as a reference which is different from ref_(a) and its temporal distance to the current picture is the minimal one in list B. After ref_(b) is determined, MVb is derived by scaling MVa based on the temporal distance between the current picture and ref_(a), ref_(b).

In some implementations, four MVs from the interpolated MV field can also be added to the CU level candidate list. More specifically, the interpolated MVs at the position (0, 0), (W/2, 0), (0, H/2) and (W/2, H/2) of the current CU are added. When FRUC is applied in AMVP mode, the original AMVP candidates are also added to CU level MV candidate set. In some implementations, at the CU level, 15 MVs for AMVP CUs and 13 MVs for merge CUs can be added to the candidate list.

The MV candidate set at sub-CU level includes an MV determined from a CU-level search, (2) top, left, top-left and top-right neighboring MVs, (3) scaled versions of collocated MVs from reference pictures, (4) one or more ATMVP candidates (e.g., up to four), and (5) one or more STMVP candidates (e.g., up to four). The scaled MVs from reference pictures are derived as follows. The reference pictures in both lists are traversed. The MVs at a collocated position of the sub-CU in a reference picture are scaled to the reference of the starting CU-level MV. ATMVP and STMVP candidates can be the four first ones. At the sub-CU level, one or more MVs (e.g., up to 17) are added to the candidate list.

Generation of an interpolated MV field. Before coding a frame, interpolated motion field is generated for the whole picture based on unilateral ME. Then the motion field may be used later as CU level or sub-CU level MV candidates.

In some embodiments, the motion field of each reference pictures in both reference lists is traversed at 4×4 block level. FIG. 21 shows an example of unilateral Motion Estimation (ME) 2100 in the FRUC method. For each 4×4 block, if the motion associated to the block passing through a 4×4 block in the current picture and the block has not been assigned any interpolated motion, the motion of the reference block is scaled to the current picture according to the temporal distance TD0 and TD1 (the same way as that of MV scaling of TMVP in HEVC) and the scaled motion is assigned to the block in the current frame. If no scaled MV is assigned to a 4×4 block, the block's motion is marked as unavailable in the interpolated motion field.

Interpolation and matching cost. When a motion vector points to a fractional sample position, motion compensated interpolation is needed. To reduce complexity, bi-linear interpolation instead of regular 8-tap HEVC interpolation can be used for both bilateral matching and template matching.

The calculation of matching cost is a bit different at different steps. When selecting the candidate from the candidate set at the CU level, the matching cost can be the absolute sum difference (SAD) of bilateral matching or template matching. After the starting MV is determined, the matching cost C of bilateral matching at sub-CU level search is calculated as follows:

C=SAD+w·(|MV _(x) −MV _(x) ^(s) |+|MV _(y) −MV _(y) ^(s)|)  Eq. (4)

Here, w is a weighting factor. In some embodiments, w can be empirically set to 4. MV and MV^(s) indicate the current MV and the starting MV, respectively. SAD may still be used as the matching cost of template matching at sub-CU level search.

In FRUC mode, MV is derived by using luma samples only. The derived motion will be used for both luma and chroma for MC inter prediction. After MV is decided, final MC is performed using 8-taps interpolation filter for luma and 4-taps interpolation filter for chroma.

MV refinement is a pattern based MV search with the criterion of bilateral matching cost or template matching cost. In the JEM, two search patterns are supported—an unrestricted center-biased diamond search (UCBDS) and an adaptive cross search for MV refinement at the CU level and sub-CU level, respectively. For both CU and sub-CU level MV refinement, the MV is directly searched at quarter luma sample MV accuracy, and this is followed by one-eighth luma sample MV refinement. The search range of MV refinement for the CU and sub-CU step are set equal to 8 luma samples.

In the bilateral matching merge mode, bi-prediction is applied because the motion information of a CU is derived based on the closest match between two blocks along the motion trajectory of the current CU in two different reference pictures. In the template matching merge mode, the encoder can choose among uni-prediction from list0, uni-prediction from list1, or bi-prediction for a CU. The selection ca be based on a template matching cost as follows:

If costBi<=factor*min (cost0, cost1)

-   -   bi-prediction is used;

Otherwise, if cost0<=cost1

-   -   uni-prediction from list0 is used;

Otherwise,

-   -   uni-prediction from list1 is used;

Here, cost0 is the SAD of list0 template matching, cost1 is the SAD of list1 template matching and costBi is the SAD of bi-prediction template matching. For example, when the value of factor is equal to 1.25, it means that the selection process is biased toward bi-prediction. The inter prediction direction selection can be applied to the CU-level template matching process.

2.8 Examples of Bi-Directional Optical Flow (BIO)

The bi-directional optical flow (BIO) method is a sample-wise motion refinement performed on top of block-wise motion compensation for bi-prediction. In some implementations, the sample-level motion refinement does not use signaling.

Let I^((k)) be the luma value from reference k (k=0, 1) after block motion compensation, and denote ∂I^((k))/∂x and ∂I^((k))/∂y as the horizontal and vertical components of the I^((k)) gradient, respectively. Assuming the optical flow is valid, the motion vector field (v_(x), v_(y)) is given by:

∂I ^((k)) /∂t+v _(x) ∂I ^((k)) /∂x+v _(y) ∂I ^((k)) /∂y=0  Eq. (5)

Combining this optical flow equation with Hermite interpolation for the motion trajectory of each sample results in a unique third-order polynomial that matches both the function values I^((k)) and derivatives ∂I^((k))/∂x and ∂I^((k))/∂y at the ends. The value of this polynomial at t=0 is the BIO prediction:

pred_(BIO)=½·(I ⁽⁰⁾ +I ⁽¹⁾ +v _(x)/2·(τ₁ ∂I ⁽¹⁾ /∂x−τ ₀ ∂I ⁽⁰⁾ /∂x)+v _(y)/2·(τ₁ ∂I ⁽¹⁾ /∂y−τ ₀ ∂I ⁽⁰⁾ /∂y))  (6)

FIG. 22 shows an example optical flow trajectory in the Bi-directional Optical flow (BIO) method. Here, τ₀ and τ₁ denote the distances to the reference frames. Distances τ₀ and τ₁ are calculated based on POC for Ref₀ and Ref₁: τ₀=POC(current)−POC(Ref₀), τ₁=POC(Ref₁)−POC(current). If both predictions come from the same time direction (either both from the past or both from the future) then the signs are different (e.g., τ₀·τ₁<0). In this case, BIO is applied if the prediction is not from the same time moment (e.g., τ₀≠τ₁). Both referenced regions have non-zero motion (e.g. MVx₀, MVy₀, MVx₁, MVy₁≠0) and the block motion vectors are proportional to the time distance (e.g. MVx₀/MVx₁=MVy₀/MVy₁=−τ₀/τ₁).

The motion vector field (v_(x), v_(y)) is determined by minimizing the difference Δ between values in points A and B. FIGS. 9A-9B show an example of intersection of motion trajectory and reference frame planes. Model uses only first linear term of a local Taylor expansion for Δ:

Δ=(I ⁽⁰⁾ −I ⁽¹⁾ ₀ +v _(x)(τ₁ ∂I ⁽¹⁾ /∂x+τ ₀ ∂I ⁽⁰⁾ /∂x)+v _(y)(τ₁ ∂I ⁽¹⁾ /∂y+τ ₀ ∂I ⁽⁰⁾ /∂y))  (7)

All values in the above equation depend on the sample location, denoted as (i′, j′). Assuming the motion is consistent in the local surrounding area, Δ can be minimized inside the (2M+1)×(2M+1) square window Ω centered on the currently predicted point (i,j), where M is equal to 2:

$\begin{matrix} {\left( {v_{x},v_{y}} \right) = {\underset{v_{x},v_{y}}{argmin}\mspace{11mu}{\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in \Omega}{\Delta^{2}\left\lbrack {i^{\prime},j^{\prime}} \right\rbrack}}}} & {{Eq}.\mspace{14mu}(8)} \end{matrix}$

For this optimization problem, the JEM uses a simplified approach making first a minimization in the vertical direction and then in the horizontal direction. This results in the following:

$\begin{matrix} {\mspace{79mu}{v_{x} = {\left( {s_{1} + r} \right) > {{m\;?\;{clip}}\mspace{11mu} 3\left( {{{- {th}}{BIO}},{thBIO},{- \frac{s_{3}}{\left( {s_{1} + r} \right)}}} \right)\text{:}0}}}} & {{Eq}.\mspace{14mu}(9)} \\ {{v_{y} = {\left( {s_{5} + r} \right) > {{m\;?\;{clip}}\mspace{11mu} 3\left( {{- {thBIO}},{thBIO},{- \frac{s_{6} - {v_{x}{s_{2}/2}}}{\left( {s_{5} + r} \right)}}} \right)\text{:}0}}}\mspace{79mu}{{where},}} & {{Eq}.\mspace{14mu}(10)} \\ {\mspace{79mu}{{{s_{1} = {\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in \Omega}\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial x}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial x}}}} \right)^{2}}};}\mspace{79mu}{{s_{3} = {\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in \Omega}{\left( {I^{(1)} - I^{(0)}} \right)\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial x}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial x}}}} \right)}}};}{{s_{2} = {\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in \Omega}{\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial x}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial x}}}} \right)\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial y}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial y}}}} \right)}}};}\mspace{79mu}{{s_{5} = {\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in \Omega}\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial y}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial y}}}} \right)^{2}}};}\mspace{79mu}{s_{6} = {\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in \Omega}{\left( {I^{(1)} - I^{(0)}} \right)\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial y}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial y}}}} \right)}}}}} & {{Eq}.\mspace{14mu}(11)} \end{matrix}$

In order to avoid division by zero or a very small value, regularization parameters r and m can be introduced in Eq. (9) and Eq. (10), where:

r=500·4^(d−8)  Eq. (12)

m=700·4^(d−8)  Eq. (13)

Here, d is bit depth of the video samples.

In order to keep the memory access for BIO the same as for regular bi-predictive motion compensation, all prediction and gradients values, I^((k)), ∂I^((k))/∂x, ∂I^((k))/∂y, are calculated for positions inside the current block. FIG. 23A shows an example of access positions outside of a block 2300. As shown in FIG. 23A, in Eq. (9), (2M+1)×(2M+1) square window Ω centered in currently predicted point on a boundary of predicted block needs to accesses positions outside of the block. In the JEM, values of I^((k)),∂I^((k))/∂x,∂I^((k))/∂y outside of the block are set to be equal to the nearest available value inside the block. For example, this can be implemented as a padding area 2301, as shown in FIG. 23B.

With BIO, it is possible that the motion field can be refined for each sample. To reduce the computational complexity, a block-based design of BIO is used in the JEM. The motion refinement can be calculated based on a 4×4 block. In the block-based BIO, the values of s_(n) in Eq. (9) of all samples in a 4×4 block can be aggregated, and then the aggregated values of s_(n) in are used to derived BIO motion vectors offset for the 4×4 block. More specifically, the following formula can used for block-based BIO derivation:

$\begin{matrix} {{{s_{1,b_{k}} = {\sum\limits_{{({x,y})} \in b_{k}}{\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in {\Omega{({x,y})}}}\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial x}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial x}}}} \right)^{2}}}};}{{s_{3,b_{k}} = {\sum\limits_{{({x,y})} \in b_{k}}{\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in \Omega}{\left( {I^{(1)} - I^{(0)}} \right)\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial x}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial x}}}} \right)}}}};}{{s_{2,b_{k}} = {\sum\limits_{{({x,y})} \in b_{k}}{\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in \Omega}{\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial x}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial x}}}} \right)\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial y}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial y}}}} \right)}}}};}{{s_{5,b_{k}} = {\sum\limits_{{({x,y})} \in b_{k}}{\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in \Omega}\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial y}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial y}}}} \right)^{2}}}};}{s_{6,b_{k}} = {\sum\limits_{{({x,y})} \in b_{k}}{\sum\limits_{{\lbrack{i^{\prime},j}\rbrack} \in \Omega}{\left( {I^{(1)} - I^{(0)}} \right)\left( {{\tau_{1}{{\partial I^{(1)}}/{\partial y}}} + {\tau_{0}{{\partial I^{(0)}}/{\partial y}}}} \right)}}}}} & {{Eq}.\mspace{14mu}(14)} \end{matrix}$

Here, b_(k) denotes the set of samples belonging to the k-th 4×4 block of the predicted block. s_(n) in Eq (9) and Eq (10) are replaced by ((s_(n,bk))>>4) to derive the associated motion vector offsets.

In some scenarios, MV regiment of BIO may be unreliable due to noise or irregular motion. Therefore, in BIO, the magnitude of MV regiment is clipped to a threshold value. The threshold value is determined based on whether the reference pictures of the current picture are all from one direction. For example, if all the reference pictures of the current picture are from one direction, the value of the threshold is set to 12×2^(14−d); otherwise, it is set to 12×2^(13−d).

Gradients for BIO can be calculated at the same time with motion compensation interpolation using operations consistent with HEVC motion compensation process (e.g., 2D separable Finite Impulse Response (FIR)). In some embodiments, the input for the 2D separable FIR is the same reference frame sample as for motion compensation process and fractional position (fracX, fracY) according to the fractional part of block motion vector. For horizontal gradient ∂I/∂x, a signal is first interpolated vertically using BIOfilterS corresponding to the fractional position fracY with de-scaling shift d−8. Gradient filter BIOfilterG is then applied in horizontal direction corresponding to the fractional position fracX with de-scaling shift by 18−d. For vertical gradient ∂I/∂y, a gradient filter is applied vertically using BIOfilterG corresponding to the fractional position fracY with de-scaling shift d−8. The signal displacement is then performed using BIOfilterS in horizontal direction corresponding to the fractional position fracX with de-scaling shift by 18−d. The length of interpolation filter for gradients calculation BIOfilterG and signal displacement BIOfilterF can be shorter (e.g., 6-tap) in order to maintain reasonable complexity. Table 1 shows example filters that can be used for gradients calculation of different fractional positions of block motion vector in BIO. Table 2 shows example interpolation filters that can be used for prediction signal generation in BIO.

TABLE 1 Exemplary filters for gradient calculations in BIO Fractional pel position Interpolation filter for gradient(BIOfilterG) 0 {8, −39, −3, 46, −17, 5} 1/16 {8, −32, −13, 50, −18, 5} 1/8 {7, −27, −20, 54, −19, 5} 3/16 {6, −21, −29, 57, −18, 5} 1/4 {4, −17, −36, 60, −15, 4} 5/16 {3, −9, −44, 61, −15, 4} 3/8 {1, −4, −48, 61, −13, 3} 7/16 {0, 1, −54, 60, −9, 2} 1/2 {−1, 4, −57, 57, −4, 1}

TABLE 2 Exemplary interpolation filters for prediction signal generation in BIO Fractional pel position Interpolation filter for prediction signal(BIOfilterS) 0 {0, 0, 64, 0, 0, 0} 1/16 {1, −3, 64, 4, −2, 0} 1/8 {1, −6, 62, 9, −3, 1} 3/16 {2, −8, 60, 14, −5, 1} 1/4 {2, −9, 57, 19, −7, 2} 5/16 {3, −10, 53, 24, −8, 2} 3/8 {3, −11, 50, 29, −9, 2} 7/16 {3, −11, 44, 35, −10, 3} 1/2 {3, −10, 35, 44, −11, 3}

In the JEM, BIO can be applied to all bi-predicted blocks when the two predictions are from different reference pictures. When Local Illumination Compensation (LIC) is enabled for a CU, BIO can be disabled.

In some embodiments, OBMC is applied for a block after normal MC process. To reduce the computational complexity, BIO may not be applied during the OBMC process. This means that BIO is applied in the MC process for a block when using its own MV and is not applied in the MC process when the MV of a neighboring block is used during the OBMC process.

2.9 Examples of Decoder-Side Motion Vector Refinement (Dmvr)

In a bi-prediction operation, for the prediction of one block region, two prediction blocks, formed using a motion vector (MV) of list0 and a MV of list1, respectively, are combined to form a single prediction signal. In the decoder-side motion vector refinement (DMVR) method, the two motion vectors of the bi-prediction are further refined by a bilateral template matching process. The bilateral template matching applied in the decoder to perform a distortion-based search between a bilateral template and the reconstruction samples in the reference pictures in order to obtain a refined MV without transmission of additional motion information.

In DMVR, a bilateral template is generated as the weighted combination (i.e. average) of the two prediction blocks, from the initial MV0 of list0 and MV1 of list1, respectively, as shown in FIG. 24. The template matching operation consists of calculating cost measures between the generated template and the sample region (around the initial prediction block) in the reference picture. For each of the two reference pictures, the MV that yields the minimum template cost is considered as the updated MV of that list to replace the original one. In the JEM, nine MV candidates are searched for each list. The nine MV candidates include the original MV and 8 surrounding MVs with one luma sample offset to the original MV in either the horizontal or vertical direction, or both. Finally, the two new MVs, i.e., MV0′ and MV1′ as shown in FIG. 24, are used for generating the final bi-prediction results. A sum of absolute differences (SAD) is used as the cost measure.

DMVR is applied for the merge mode of bi-prediction with one MV from a reference picture in the past and another from a reference picture in the future, without the transmission of additional syntax elements. In the JEM, when LIC, affine motion, FRUC, or sub-CU merge candidate is enabled for a CU, DMVR is not applied.

2.2.9 Examples of Symmetric Motion Vector Difference

In [8], symmetric motion vector difference (SMVD) is proposed to encode the MVD more efficiently.

Firstly, in slice level, variables BiDirPredFlag, RefIdxSymL0 and RefIdxSymL1 are derived as follows:

The forward reference picture in reference picture list0 which is nearest to the current picture is searched. If found, RefIdxSymL0 is set equal to the reference index of the forward picture.

The backward reference picture in reference picture list1 which is nearest to the current picture is searched. If found, RefIdxSymL1 is set equal to the reference index of the backward picture.

If both forward and backward picture are found, BiDirPredFlag is set equal to 1.

Otherwise, following applies:

The backward reference picture in reference picture list0 which is nearest to the current one is searched. If found, RefIdxSymL0 is set equal to the reference index of the backward picture.

The forward reference picture in reference picture list1 which is nearest to the current one is searched. If found, RefIdxSymL1 is set equal to the reference index of the forward picture.

If both backward and forward picture are found, BiDirPredFlag is set equal to 1. Otherwise, BiDirPredFlag is set equal to 0.

Secondly, in CU level, a symmetrical mode flag indicating whether symmetrical mode is used or not is explicitly signaled if the prediction direction for the CU is bi-prediction and BiDirPredFlag is equal to 1.

When the flag is true, only mvp_10_flag, mvp_11_flag and MVD0 are explicitly signaled. The reference indices are set equal to RefIdxSymL0, RefIdxSymL1 for list0 and list1, respectively. MVD1 is just set equal to −MVD0. The final motion vectors are shown in below formula.

$\quad\left\{ \begin{matrix} {\left( {{{mv}x_{0}},{{mv}y_{0}}} \right) = \left( {{{mvpx_{0}} + {mvdx_{0}}},{{{mvp}y_{0}} + {mvdy_{0}}}} \right)} \\ {\left( {{{mv}x_{1}},{{mv}y_{1}}} \right) = \left( {{{mvpx_{1}} - {mvdx_{0}}},{{{mvp}y_{1}} - {mvdy_{0}}}} \right)} \end{matrix} \right.$

FIG. 27 shows examples of symmetrical mode.

The modifications in coding unit syntax are shown in Table 3.

TABLE 3 Modifications in coding unit syntax Descriptor coding_unit( x0, y0, cbWidth, cbHeight, treeType ) { . . .    if( slice_type == B )     inter_pred_idc[ x0 ][ y0 ] ae(v)    if( sps_affine_enabled_flag && cbWidth >= 16 && cbHeight >= 16 ) {     inter_affine_flag[ x0 ][ y0 ] ae(v)     if( sps_affine_type_flag &&     inter_affine_flag[ x0 ][ y0 ] )      cu_affine_type_flag[ x0 ][ y0 ] ae(v)    }    if( inter_pred_idc[ x0 ][ y0 ] == PRED_BI &&     BiDirPredFlag && inter_affine_flag[ x0 ][ y0 ] == 0 )     symmetric_mvd_flag[ x0 ][ y0 ] ae(v)    if( inter_pred_idc[ x0 ][ y0 ] != PRED_L1 ) {     if( num_ref_idx_l0_active_minus1 > 0 && !symmetric_mvd_flag[ x0 ][ y0 ] )      ref_idx_l0[ x0 ][ y0 ] ae(v)     mvd_coding( x0, y0, 0, 0 )     if( MotionModelIdc[ x0 ][ y0 ] > 0 )      mvd_coding( x0, y0, 0, 1 )     if(MotionModelIdc[ x0 ][ y0 ] > 1 )      mvd_coding( x0, y0, 0, 2 )     mvp_l0_flag[ x0 ][ y0 ] ae(v)    } else {     MvdL0[ x0 ][ y0 ][ 0 ] = 0     MvdL0[ x0 ][ y0 ][ 1 ] = 0    }    if( inter_pred_idc[ x0 ][ y0 ] != PRED_L0 ) {     if( num_ref_idx_l1_active_minus1 > 0 && !symmetric_mvd_flag[ x0 ][ y0 ] )      ref_idx_l1[ x0 ][ y0 ] ae(v)     if( mvd_l1_zero_flag && inter_pred_idc[ x0 ][ y0 ] == PRED_BI ) {      . . .     } else {      if( !symmetric_mvd_flag[ x0 ][ y0 ] ) {       mvd_coding( x0, y0, 1, 0 )      if( MotionModelIdc[ x0 ][ y0 ] > 0 )       mvd_coding( x0, y0, 1, 1 )      if(MotionModelIdc[ x0 ][ y0 ] > 1 )       mvd_coding( x0, y0, 1, 2 )     }     mvp_l1_flag[ x0 ][ y0 ] ae(v)    } else {     MvdL1[ x0 ][ y0 ][ 0 ] = 0     MvdL1[ x0 ][ y0 ][ 1 ] = 0    }    . . .   }  }  . . . }

2.2.11 Symmetric MVD for Affine Bi-Prediction Coding

SMVD for affine mode is proposed in [9].

2.3 Context-Adaptive Binary Arithmetic Coding (CABAC) 2.3.1 CABAC Design in HEVC 2.3.1.1 Context Representation and Initialization Process in HEVC

In HEVC, for each context variable, the two variables pStateIdx and valMps are initialized.

From the 8 bit table entry initValue, the two 4 bit variables slopeIdx and offsetIdx are derived as follows:

slopeIdx=initValue>>4

offsetIdx=initValue&15   (34)

The variables m and n, used in the initialization of context variables, are derived from slopeIdx and offsetIdx as follows:

m=slopeIdx*5−45

n=(offsetIdx<<3)−16   (35)

The two values assigned to pStateIdx and valMps for the initialization are derived from the luma's quantization parameter of slice denoted by SliceQpY. Given the variables m and n, the initialization is specified as follows:

preCtxState=Clip3(1,126,((m*Clip3(0,51,SliceQpY))>>4)+n)

valMps=(preCtxState<=63)?0:1  (36)

pStateIdx=valMps?(preCtxState−64):(63−preCtxState)

2.3.1.2 State Transition Process in HEVC

Inputs to this process are the current pStateIdx, the decoded value binVal and valMps values of the context variable associated with ctxTable and ctxIdx.

Outputs of this process are the updated pStateIdx and valMps of the context variable associated with ctxIdx.

Depending on the decoded value binVal, the update of the two variables pStateIdx and valMps associated with ctxIdx is derived as follows in (37):

  if( binVal = = valMps )  pStateIdx = transIdxMps( pStateIdx ) else {  if( pStateIdx = = 0 ) valMps = 1 □ valMps  pStateIdx = transIdxLps( pStateIdx ) }

2.3.2 CABAC Design in VVC

The context-adaptive binary arithmetic coder (BAC) in VVC has been changed in VVC which is different from that in HEVC in terms of both context updating process and arithmetic coder.

Here is the summary of recently adopted proposal (JVET-M0473, CE test 5.1.13).

TABLE 4 Summary of CABAC modifications in VVC State representation 10 + 14 bit linear, reduced range rLPS computation 5 × 4 bit multiplier Initialization 128 × 16 bit to map HEVC-like state to linear representation, retrained initialization values Rate estimation 256 × 2 × 19 bit table Window size Variable, defined per context a = 2 . . . 5 (controlling b = a + 3 . . . 6 probability updating speed) That is, each context has two variables for recording the associated probabilities, and each probability is updated with its own speed (faster speed based on the variable a and lower speed based on the variable b) Other rMPS >= 128 is guaranteed

2.3.2.1 Context Initialization Process in VVC

n VVC, two values assigned to pStateIdx0 and pStateIdx1 for the initialization are derived from SliceQpY. Given the variables m and n, the initialization is specified as follows:

preCtxState=Clip3(0,127,((m*Clip3(0,51,SliceQpY))>>4)+n)

pStateIdx0=initStateIdxToState[preCtxState]>>4

pStateIdx1=initStateIdxToState[preCtxState]  (38)

2.3.2.2 State Transition Process in VVC

Inputs to this process are the current pStateIdx0 and pStateIdx1, and the decoded value binVal.

Outputs of this process are the updated pStateIdx0 and pStateIdx1 of the context variable associated with ctxIdx.

The variables shift0 (corresponding to variable a in Summary of CABAC modifications in VVCTable 4) and shift 1 (corresponding to variable b in Summary of CABAC modifications in VVC Table 4e) are derived from the shiftIdx value associated with ctxTable and ctxInc.

shift0=(shiftIdx>>2)+2

shift1=(shiftIdx&3)+3+shift0  (39)

Depending on the decoded value binVal, the update of the two variables pStateIdx0 and pStateIdx1 associated with ctxIdx is derived as follows:

pStateIdx0=pStateIdx0□(pStateIdx0>>shift0)+(1023*binVal>>shift0)

pStateIdx1=pStateIdx1□(pStateIdx1>>shift1)+(16383*binVal>>shift1)  (40)

3. Drawbacks of Existing Implementations

In some existing implementations, when MV/MV difference (MVD) could be selected from a set of multiple MV/MVD precisions for affine coded blocks, it remains uncertain how more accurate motion vectors may be obtained.

In other existing implementations, the MV/MVD precision information also plays an important role in determination of the overall coding gain of AMVR applied to affine mode, but achieving this goal remains uncertain.

4. Example Methods for MV Predictors for Affine Mode with AMVR

Embodiments of the presently disclosed technology overcome the drawbacks of existing implementations, thereby providing video coding with higher coding efficiencies. The derivation and signaling of motion vector predictors for affine mode with adaptive motion vector resolution (AMVR), based on the disclosed technology, may enhance both existing and future video coding standards, is elucidated in the following examples described for various implementations. The examples of the disclosed technology provided below explain general concepts, and are not meant to be interpreted as limiting. In an example, unless explicitly indicated to the contrary, the various features described in these examples may be combined.

In some embodiments, the following examples may be applied to affine mode or normal mode when AMVR is applied. These examples assume that a precision Prec (i.e., MV is with 1/(2{circumflex over ( )}Prec) precision) is used for encoding MVD in AF_INTER mode or for encoding MVD in normal inter mode. A motion vector predictor (e.g., inherited from a neighboring block MV) and its precision are denoted by MVPred(MVPredx, MVPredy) and PredPrec, respectively.

In the following discussion, SatShift(x, n) is defined as

${{SatShift}\;\left( {x,n} \right)} = \left\{ \begin{matrix} {\left( {x + {{offsset}\mspace{14mu} 0}} \right)\operatorname{>>}{{{n\ }\mspace{11mu}{if}\mspace{14mu} x} \geq 0}} \\ {{{- \left( {\left( {{- x} + {{offset}\mspace{14mu} 1}} \right)\operatorname{>>}n} \right)}\mspace{14mu}{if}\mspace{14mu} x} < 0} \end{matrix} \right.$

Shift(x, n) is defined as Shift(x, n)=(x+offset0)>>n. In one example, offset0 and/or offset1 are set to (1<<n)>>1 or (1<<(n−1)). In another example, offset0 and/or offset1 are set to 0. In another example, offset0=offset1=((1<<n)>>1)−1 or ((1<<(n−1)))−1.

In the following discussion, an operation between two motion vectors means the operation will be applied to both the two components of the motion vector. For example, MV3=MV1+MV2 is equivalent to MV3x=MV1x+MV2x and MV3y=MV1y+MV2y. alternatively, the operation may be only applied to the horizontal or vertical component of the two motion vectors.

Example 1

It is proposed that final MV precision may be kept unchanged, i.e., same as the precision of motion vectors to be stored.

-   -   (a) In one example, the final MV precision may be set to         1/16-pel or ⅛-pel.     -   (b) In one example, the signaled MVD may be firstly scaled and         then added to the MVP to form the final MV for one block.

Example 2

The MVP directly derived from neighboring blocks (e.g., spatial or temporal) or default MVPs may be firstly modified and then added to the signaled MVD to form the final MV for a (current) block.

-   -   (a) Alternatively, whether to apply and how to apply         modifications of MVP may be different for different values of         Prec.     -   (b) In one example, if Prec is greater than 1 (i.e., MVD is with         fractional precision), precision of the neighboring MV is not         changed and the scaling is not performed.     -   (c) In one example, if Prec is equal to 1 (i.e., MVD is with         1-pel precision), MV predictor (i.e., neighboring blocks' MV)         need to be scaled, e.g., according to Example 4(b) of PCT         Application PCT/CN2018/104723.     -   (d) In one example, if Prec is smaller than 1 (i.e., MVD is with         4-pel precision), MV predictor (i.e., neighboring blocks' MV)         need to be scaled, e.g., according to Example 4(b) of PCT         Application PCT/CN2018/104723.

Example 3

In one example, if the precision of MVD signaled is the same as the precision of stored MVs, no scaling is needed after the affine MVs are reconstructed, Otherwise, the MV is reconstructed with the precision of the signaled MVD and then scaled to the precision of the stored MVs.

Example 4

In one example, normal inter mode and AF_INTER mode may choose implementations based on the different examples described above.

Example 5

In one example, a syntax element to indicate the MV/MVD precisions for affine mode may be signaled, with the following semantics:

-   -   (a) In one example, the syntax element equal to 0, 1 and 2         indicates ¼-pel, 1/16-pel and 1-pel MV precision respectively.     -   (b) Alternatively, in affine mode, the syntax element equal to         0, 1 and 2 indicates ¼-pel, 1-pel and 1/16-pel MV precision         respectively.     -   (c) Alternatively, in affine mode, the syntax element equal to         0, 1 and 2 indicates 1/16-pel, ¼-pel and 1-pel MV precision         respectively.

Example 6

In one example, whether to enable or disable AMVR for affine mode may be signaled in SPS, PPS, VPS, sequence/picture/slice header/tile, etc. al.

Example 7

In one example, indications of allowed MV/MVD precisions may be signaled in SPS, PPS, VPS, sequence/picture/slice header/tile, etc.

-   -   (a) Indications of selected MVD precision may be signaled for         each coding tree unit (CTU) and/or each region.     -   (b) The set of allowed MV/MVD precisions may depend on the coded         mode of the current block (e.g., affine or non-affine).     -   (c) The set of allowed MV/MVD precisions may depend on slice         type/temporal layer index/low delay check flag.     -   (d) The set of allowed MV/MVD precisions may depend on block         size and/or block shapes of the current or a neighboring block.     -   (e) The set of allowed MV/MVD precisions may depend on the         precision of MVs to be stored in decoded picture buffer.         -   (i) In one example, if the stored MV is in X-pel, the             allowed MV/MVD precision set may at least have X-pel.             Improvement of Affine Mode with AMVR Supported

Example 8

The set of allowed MVD precisions may be different from picture to picture, from slice to slice, or from block to block.

-   -   a. In one example, the set of allowed MVD precisions may depend         on coded information, such as block size, block shape. etc. al.     -   b. A set of allowed MV precisions may be pre-defined, such as {         1/16, ¼, 1}.     -   c. Indications of allowed MV precisions may be signaled in         SPS/PPS/VPS/sequence header/picture header/slice header/group of         CTUs, etc. al.     -   d. The signaling of selected MV precision from a set of allowed         MV precisions further depend on number of allowed MV precisions         for a block.

Example 9

A syntax element is signaled to the decoder to indicate the used MVD precision in affine inter mode.

a. In one example, only one single syntax element is used to indicate the MVD precisions applied to the affine mode and the AMVR mode.

-   i. In one example, same semantics are used, that is, the same value     of syntax element is mapped to the same MVD precision for the AMVR     and affine mode. -   ii. Alternatively, the semantics of the single syntax element is     different for the AMVR mode and the affine mode. That is, the same     value of syntax element could be mapped to different MVD precision     for the AMVR and affine mode.     b. In one example, when affine mode uses same set of MVD precisions     with AMVR (e.g., MVD precision set is {1, ¼, 4}-pel), the MVD     precision syntax element in AMVR is reused in affine mode, i.e.,     only one single syntax element is used. -   i. Alternatively, furthermore, when encoding/decoding this syntax     element in CABAC encoder/decoder, same or different context models     may be used for AMVR and affine mode. -   ii. Alternatively, furthermore, this syntax element may have     different semantics in AMVR and affine mode. For example, the syntax     element equal to 0, 1 and 2 indicates ¼-pel, 1-pel and 4-pel MV     precision respectively in AMVR, while in affine mode, the syntax     element equal to 0, 1 and 2 indicates ¼-pel, 1/16-pel and 1-pel MV     precision respectively.     c. In one example, when affine mode uses same number of MVD     precisions with AMVR but different sets of MVD precisions (e.g., MVD     precision set for AMVR is {1, ¼, 4}-pel while for affine, it is {     1/16, ¼, 1}-pel), the MVD precision syntax element in AMVR is reused     in affine mode, i.e., only one single syntax element is used. -   i. Alternatively, furthermore, when encoding/decoding this syntax     element in CABAC encoder/decoder, same or different context models     may be used for AMVR and affine mode. -   ii. Alternatively, furthermore, this syntax element may have     different semantics in AMVR and affine mode.     d. In one example, affine mode uses less MVD precisions than AMVR,     the MVD precision syntax element in AMVR is reused in affine mode.     However, only a subset of the syntax element values is valid for     affine mode. -   i. Alternatively, furthermore, when encoding/decoding this syntax     element in CABAC encoder/decoder, same or different context models     may be used for AMVR and affine mode. -   ii. Alternatively, furthermore, this syntax element may have     different semantics in AMVR and affine mode.     e. In one example, affine mode uses more MVD precisions than AMVR,     the MVD precision syntax element in AMVR is reused in affine mode.     However, such syntax element is extended to allow more values in     affine mode. -   i. Alternatively, furthermore, when encoding/decoding this syntax     element in CABAC encoder/decoder, same or different context models     may be used for AMVR and affine mode. -   ii. Alternatively, furthermore, this syntax element may have     different semantics in AMVR and affine mode.     f. In one example, a new syntax element is used for coding the MVD     precision of affine mode, i.e., two different syntax elements are     used for coding the MVD precision of AMVR and affine mode.     g. The syntax for indication of MVD precisions for the affine mode     may be signaled under one or all of the following conditions are     true: -   i. MVDs for all control points are non-zero. -   ii. MVDs for at least one control point is non-zero. -   iii. MVD of one control point (e.g., the first CPMV) are non-zero     In this case, when either one of the above conditions or all of them     fail, there is no need to signal the MVD precisions.     h. The syntax element for indication of MVD precisions for either     affine mode or the AMVR mode may be coded with contexts and the     contexts are dependent on coded information. -   i. In one example, when there is only one single syntax element, the     contexts may depend on whether current block is coded with affine     mode or not.     i. In one example, the context may depend on the block size/block     shape/MVD precisions of neighboring blocks/temporal layer     index/prediction directions, etc. al.     j. Whether to enable or disable the usage of multiple MVD precisions     for the affine mode may be signaled in SPS/PPS/VPS/sequence     header/picture header/slice header/group of CTUs, etc. al. -   i. In one example, whether to signal the information of enable or     disable the usage of multiple MVD precisions for the affine mode may     depend on other syntax elements. For example, the information of     enable or disable the usage of multiple MV and/or MVP and/or MVD     precisions for the affine mode is signaled when affine mode is     enabled; and is not signaled and inferred to be 0 when affine mode     is disabled.     k. Alternatively, multiple syntax elements may be signaled to     indicate the used MV and/or MVP and/or MVD precision (in the     following discussion, they are all referred to as “MVD precision”)     in affine inter mode. -   i. In one example, the syntax elements used to indicate the used MVD     precision in affine inter mode and normal inter mode may be     different.     -   1. The number of syntax elements to indicate the used MVD         precision in affine inter mode and normal inter mode may be         different.     -   2. The semantics of the syntax elements to indicate the used MVD         precision in affine inter mode and normal inter mode may be         different.     -   3. The context models in arithmetic coding to code one syntax         elements to indicate the used MVD precision in affine inter mode         and normal inter mode may be different.     -   4. The methods to derive context models in arithmetic coding to         code one syntax element to indicate the used MVD precision in         affine inter mode and normal inter mode may be different. -   ii. In one example, a first syntax element (e.g. amvr_flag) may be     signaled to indicate whether to apply AMVR in an affine-coded block.     -   1. The first syntax element is conditionally signaled.         -   a. In one example, signalling of the first syntax element             (amvr_flag) is skipped when current block is coded with             certain mode (e.g., CPR/IBC mode).         -   b. In one example, signalling of the first syntax element             (amvr_flag) is skipped when all CPMVs' MVDs (including both             horizontal and vertical components) are all zero.         -   c. In one example, signalling of the first syntax element             (amvr_flag) is skipped when one selected CPMVs' MVDs             (including both horizontal and vertical components) are all             zero.             -   i. In one example, the selected CPMV's MVD is the first                 CPMV's MVD to be coded/decoded.         -   d. In one example, signalling of the first syntax element             (amvr_flag) is skipped when the usage of enabling multiple             MVD precisions for affine-coded block is false.         -   e. In one example, the first syntax element may be signaled             under the following conditions:             -   i. Usage of enabling multiple MVD precisions for                 affine-coded block is true and current block is coded                 with affine mode;             -   ii. Alternatively, usage of enabling multiple MVD                 precisions for affine-coded block is true, current block                 is coded with affine mode, and at least one component of                 a CPMV's MVD is unequal to 0.             -   iii. Alternatively, usage of enabling multiple MVD                 precisions for affine-coded block is true, current block                 is coded with affine mode, and at least one component of                 a selected CPMV's MVD is unequal to 0.                 -   1. In one example, the selected CPMV's MVD is the                     first CPMV's MVD to be coded/decoded.     -   2. When AMVR is not applied to an affine-coded block or the         first syntax element is not present, a default MV and/or MVD         precision is utilized.         -   f. In one example, the default precision is ¼-pel.         -   g. Alternatively, the default precision is set to that used             in motion compensation for affine coded blocks.     -   3. For example, the MVD precision of affine mode is ¼-pel if         amvr_flag is equal to 0; otherwise the MVD precision of affine         mode may be other values.         -   h. Alternatively, furthermore, the additional MVD precisions             may be further signaled via a second syntax element. -   iii. In one example, a second syntax element (such as amvr_coarse     _precision_flag) may be signaled to indicate the MVD precision of     affine mode.     -   1. In one example, whether the second syntax element is signaled         may depend on the first syntax element. For example, the second         syntax element is only signaled when the first syntax element is         1.     -   2. In one example, the MVD precision of affine mode is 1-pel if         the second syntax element is 0; otherwise, the MVD precision of         affine mode is 1/16-pel.     -   3. In one example, the MVD precision of affine mode is 1/16-pel         if the second syntax element is 0; otherwise, the MVD precision         of affine mode is full-pixel. -   iv. In one example, a syntax element used to indicate the used MVD     precision in affine inter mode share the same context models as the     syntax element with the same name but used to indicate the used MVD     precision in normal inter mode.     -   4. Alternatively, a syntax element used to indicate the used MVD         precision in affine inter mode use different context models as         the syntax element with the same name but used to indicate the         used MVD precision in normal inter mode.

Example 10

Whether to apply or how to apply AMVR on an affine coded block may depend on the reference picture of the current block.

-   -   a. In one example, AMVR is not applied if the reference picture         is the current picture, i.e., Intra block copying is applied in         the current block.

Fast Algorithm of AVMR in Affine Mode for Encoder

Denote RD cost (real RD cost, or SATD/SSE/SAD cost plus rough bits cost) of affine mode and AMVP mode as affineCosti and amvpCosti for IMV=i, where in i=0, 1 or 2. Here, IMV=0 means ¼ pel MV, and IMV=1 means integer MV for AMVP mode and 1/16 pel MV for affine mode, and IMV=2 means 4 pel MV for AMVP mode and integer MV for affine mode. Denote RD cost of merge mode as mergeCost.

Example 11

It is proposed that AMVR is disabled for affine mode of current CU if the best mode of its parent CU is not AF_INTER mode or AF_MERGE mode.

Alternatively, AMVR is disabled for affine mode of current CU if the best mode of its parent CU is not AF_INTER modeExample 12. It is proposed that AMVR is disabled for affine mode if affineCost0>th1*amvpCost0, wherein th1 is a positive threshold.

-   -   a. Alternatively, in addition, AMVR is disabled for affine mode         if min(affineCost0, amvpCost0)>th2*mergeCost, wherein th2 is a         positive threshold.     -   b. Alternatively, in addition, integer MV is disabled for affine         mode if affineCost0>th3*affineCostl, wherein th3 is a positive         threshold.

Example 12

It is proposed that AMVR is disabled for AMVP mode if amvpCost0>th4*affineCost0, wherein th4 is a positive threshold.

-   -   a. Alternatively, AMVR is disabled for AMVP mode if         min(affineCost0, amvpCost0)>th5*mergeCost, wherein th5 is a         positive threshold.

Example 13

It is proposed that 4/6 parameter affine models obtained in one MV precision may be used as a candidate start search point for other MV precisions.

-   -   b. In one example, 4/6 parameter affine models obtained in 1/16         MV may be used as a candidate start search point for other MV         precisions.     -   c. In one example, 4/6 parameter affine models obtained in ¼ MV         may be used as a candidate start search point for other MV         precisions.

Example 14

AMVR for affine mode is not checked at encoder for the current block if its parent block does not choose the affine mode.

Example 15

Statistics of usage of different MV precisions for affine-coded blocks in previously coded frames/slices/tiles/CTU rows may be utilized to early terminate the rate-distortion calculations of MV precisions for affine-coded blocks in current slice/tile/CTU row.

-   -   d. In one example, the percentage of affine-coded blocks with a         certain MV precision is recorded. If the percentage is too low,         then the checking of the corresponding MV precision is skipped.     -   e. In one example, previously coded frames with the same         temporal layer are utilized to decide whether to skip a certain         MV precision.

Context for Coding Affine AMVR Example 16

For each context that is used for coding the affine AMVR code, it is proposed to set a variable (denoted by shiftIdx) to control two probability updating speed associated with this context.

-   -   a. In one example, the faster updating speed is defined by         (shiftIdx>>2)+2.     -   b. In one example, the slower updating speed is defined by         (shiftIdx & 3)+3+shift0     -   c. In one example, the conformance bitstream shall follow the         rule that the derived faster updating speed shall be within [2,         5] inclusively.     -   d. In one example, the conformance bitstream shall follow the         rule that the derived faster updating speed shall be within [3,         6] inclusively.

Example 17

It is proposed that when coding the AMVR mode of one block, the neighboring block's affine AMVR mode information is disallowed for context modeling.

-   -   a. In one example, the neighboring block's AMVR mode index may         be utilized and neighboring block's affine AMVR mode information         is excluded. An example is shown in Table 1 (including Table 5-1         and 5-2), wherein (xNbL, yNbL) and (xNbA, yNbA) denotes the left         and above neighboring block. In one example, the context index         offset ctxInc=(condL && availableL)+(condA &&         availableA)+ctxSetIdx*3.

TABLE 1-1 Specification of ctxInc using left and above syntax elements Syntax element condL condA ctxSetIdx amvr_mode[ x0 ][ y0 ] amvr_mode[ xNbL ][ yNbL ] amvr_mode[ xNbA ][ yNbA ] 0 ( inter_affine_flag[ x0 ][ y0 ] && !inter_affine_flag[ xNbL ][ yNbL ] && !inter_affine_flag[ xNbL ][ yNbL ] is equal to 0 )

TABLE 2-2 Specification of ctxInc using left and above syntax elements Syntax element condL condA ctxSetIdx amvr_mode[ x0 ][ y0 ] amvr_mode[ xNbL ][ yNbL ] amvr_mode[ xNbA ][ yNbA ] 0 ( inter_affine_flag[ x0 ] && !inter_affine_flag[ xNbL ] && !inter_affine_flag[ xNbL ] [ y0 ] is equal to 0 ) [ yNbL ] [ yNbL ]

-   -   b. Alternatively, neighboring block's affine AMVR mode         information may be further utilized but with a function instead         of being directly used. In one example, the function func as         described in Table 3-1 may return true when the amvr_mode[xNbL]         [yNbL] of an affine-coded neighboring block indicates a certain         MV precision (such as the ¼-pel MV precision). In one example,         the function func as described in Table 3-2 may return true when         the amvr_flag[xNbL] [yNbL] of an affine-coded neighboring block         indicates a certain MV precision (such as the ¼-pel MV         precision).

TABLE 3-1 Specification of ctxInc using left and above syntax elements Syntax element condL condA ctxSetIdx amvr_mode[ x0 ][ y0 ] (amvr_mode[ xNbL ][ yNbL ] amvr_mode[ xNbA ][ yNbA ] 0 ( inter_affine_flag[ x0 ] && !inter_affine_flag[ xNbL ][ yNbL ]) && !inter_affine_flag[ xNbL ][ yNbL ] [ y0 ] is equal to 0 ) ||( inter_affine_flag[ xNbL ][ yNbL ] && ||(inter_affine_flag[ xNbL ][ yNbL ] && func(amvr_mode[ xNbL ][ yNbL ])) func(amvr_mode[ xNbL ][ yNbL ]))

TABLE 6-2 Specification of ctxInc using left and above syntax elements Syntax element condL condA ctxSetIdx amvr_flag[ x0 ][ y0 ] amvr_flag[ xNbL ][ yNbL ] amvr_flag[ xNbA ][ yNbA ] 0 ( inter_affine_flag[ x0 ] && !inter_affine_flag[ xNbL ] && !inter_affine_flag[ xNbL ] [ y0 ] is equal to 0 ) [ yNbL ] [ yNbL ]

-   -   -   c. Alternatively, neighboring block's affine AMVR mode             information may be further utilized for coding the first             syntax element (e.g., amvr_flag) of the AMVR mode (which is             applied to normal inter mode). Table 6-3 and 6-4 give some             examples.

TABLE 6-3 Specification of ctxInc using left and above syntax elements Syntax element condL condA ctxSetIdx amvr_flag[ x0 ][ y0 ] amvr_flag[ xNbL ][ yNbL ] amvr_flag[ xNbA ][ yNbA ] 0 ( inter_affine_flag[ x0 ][ y0 ] is equal to 0 )

TABLE 6-4 Specification of ctxInc using left and above syntax elements Syntax element condL condA ctxSetIdx amvr_flag[ x0 ][ y0 ] amvr_flag[ xNbL ][ yNbL ] amvr_flag[ xNbA ][ yNbA ] 0 && ! inter_affine_flag[ x0 ] && ! inter_affine_flag[ x0 ] [ y0 ] [ y0 ]

-   -   d. When the AMVR mode information is represented by multiple         syntax elements (e.g., the first and second syntax elements,         denoted by amvr_flag, amvr_coarse _precision_flag), the above         syntax amvr_mode may be replaced by any of the multiple syntax         elements and above methods may be still applied.

Example 18

It is proposed that when coding the Affine AMVR mode, the neighboring block's AMVR mode information may be utilized for context coding.

-   -   a. In one example, the neighboring block's AMVR mode information         is directly used. An example is shown in Table 4. Alternatively,         furthermore, the context index offset ctxInc=(condL &&         availableL)+(condA && availableA)+ctxSetIdx*3.

TABLE 4 Specification of ctxInc using left and above syntax elements Syntax element condL condA ctxSetIdx amvr_mode[ x0 ][ y0 ] amvr_mode[ xNbL ][ yNbL ] amvr_mode[ xNbA ][ yNbA ] 0 ( inter_affine_flag[ x0 ] [ y0 ] is equal to 1 )

-   -   b. Alternatively, the neighboring block's AMVR mode information         is disallowed for context modeling. An example is shown in Table         5.

TABLE 5 Specification of ctxInc using left and above syntax elements Syntax element condL condA ctxSetIdx amvr_mode[ x0 ][ y0 ] amvr_mode[ xNbL ][ yNbL ] amvr_mode[ xNbA ][ yNbA ] 0 ( inter_affine_flag[ x0 ] && inter_affine_flag[ xNbL ] && inter_affine_flag[ xNbL ] [ y0 ] is equal to 1 ) [ yNbL ] [ yNbL ]

-   -   c. Alternatively, neighboring block's AMVR mode information may         be further utilized but with a function instead of being         directly used. In one example, the function func as described in         Table 6 may return true when the amvr_mode[xNbL] [yNbL] of an         non-affine-coded neighboring block indicates a certain MV         precision (such as the ¼-pel MV precision).

TABLE 6 Specification of ctxInc using left and above syntax elements Syntax element condL condA ctxSetIdx amvr_mode[ x0 ][ y0 ] (amvr_mode[ xNbL ][ yNbL ] && amvr_mode[ xNbA ][ yNbA ] && 0 ( inter_affine_flag[ x0 ][ y0 ] inter_affine_flag[ xNbL ][ yNbL ]) inter_affine_flag[ xNbL ][ yNbL ] is equal to 1 ) ||( !inter_afffine_flag[ xNbL ][ yNbL ] && ||( !inter_afffine_flag[ xNbL ][ yNbL ] && func(amvr_mode[ xNbL ][ yNbL ])) func(amvr_mode[ xNbL ][ yNbL ]))

-   -   d. When the affine AMVR mode information is represented by         multiple syntax elements (e.g., the first and second syntax         elements, denoted by amvr_flag, amvr_coarse _precision_flag),         the above syntax amvr_mode may be replaced by any of the         multiple syntax elements and above methods may be still applied.

Fast Algorithm of SMVD and Affine SMVD

When checking the SMVD mode, suppose the currently selected best mode is CurBestMode, and the AMVR MVD precision in AMVR is MvdPrec or the MVD precision of affine AMVR is MvdPrecAff.

Example 19

SMVD mode may be skipped depending on the currently selected best mode (i.e., CurBestMode), the MVD precision in AMVR.

-   -   a. In one example, if the CurBestMode is merge mode or/and UMVE         mode, SMVD mode may be not checked.     -   b. In one example, if the CurBestMode is not coded with SMVD         mode, SMVD mode may be not checked.     -   c. In one example, if the CurBestMode is affine mode, SMVD mode         may be not checked.     -   d. In one example, if the CurBestMode is sub-block merge mode,         SMVD mode may be not checked.     -   e. In one example, if the CurBestMode is affine SMVD mode, SMVD         mode may be not checked.     -   f. In one example, if the CurBestMode is affine merge mode, SMVD         mode may be not checked.     -   g. In one example, above fast methods, i.e., bullet 0.a-0.f, may         be applied only for some MVD precision.         -   i. In one example, above fast methods may be applied only             when MVD precision is greater than or equal to a precision             (for example, integer-pel precision).         -   ii. In one example, above fast methods may be applied only             when MVD precision is greater than a precision (for example,             integer-pel precision).         -   iii. In one example, above fast methods may be applied only             when MVD precision is smaller than or equal to a precision             (for example, integer-pel precision).         -   iv. In one example, above fast methods may be applied only             when MVD precision is smaller than a precision (for example,             integer-pel precision).

Example 20

Affine SMVD mode may be skipped depending on the currently selected best mode (i.e., CurBestMode), the MVD precision in affine AMVR.

-   -   a. In one example, if the CurBestMode is merge mode or/and UMVE         mode, affine SMVD mode may be not checked.     -   b. In one example, if the CurBestMode is not coded with affine         SMVD mode, affine SMVD mode may be not checked.     -   c. In one example, if the CurBestMode is sub-block merge mode,         affine SMVD mode may be not checked.     -   d. In one example, if the CurBestMode is SMVD mode, affine SMVD         mode may be not checked.     -   e. In one example, if the CurBestMode is affine merge mode,         affine SMVD mode may be not checked.     -   f. In one example, above fast methods, i.e., bullet 20.a to         20.e, may be applied only for some MVD precision.         -   i. In one example, above fast methods may be applied only             when affine MVD precision is greater than or equal to a             precision (for example, integer-pel precision).         -   ii. In one example, above fast methods may be applied only             when affine MVD precision is greater than a precision (for             example, integer-pel precision).         -   iii. In one example, above fast methods may be applied only             when affine MVD precision is smaller than or equal to a             precision (for example, integer-pel precision).         -   iv. In one example, above fast methods may be applied only             when affine MVD precision is smaller than a precision (for             example, integer-pel precision).

Example 21

The above proposed method may be applied under certain conditions, such as block sizes, slice/picture/tile types, or motion information.

-   -   a. In one example, when a block size contains smaller than M*H         samples, e.g., 16 or 32 or 64 luma samples, proposed method is         not allowed.     -   b. Alternatively, when minimum size of a block's width or/and         height is smaller than or no larger than X, proposed method is         not allowed. In one example, X is set to 8.     -   c. Alternatively, when minimum size of a block's width or/and         height is no smaller than X, proposed method is not allowed. In         one example, X is set to 8.     -   d. Alternatively, when a block's width>th1 or >=th1 and/or a         block's height>th2 or >=th2, proposed method is not allowed. In         one example, th1 and/or th2 is set to 8.     -   e. Alternatively, when a block's width<th1 or <=th1 and/or a         block's height<th2 or <a=th2, proposed method is not allowed. In         one example, th1 and/or th2 is set to 8.     -   f. Alternatively, whether to enable or disable the above methods         and/or which method to be applied may be dependent on block         dimension, video processing data unit (VPDU), picture type, low         delay check flag, coded information of current block (such as         reference pictures, uni or bi-prediction) or previously coded         blocks.

Example 22

The AMVR methods for affine mode may be performed in different ways when intra block copy (IBC, a.k.a. current picture reference (CPR)) is applied or not.

-   -   a. In one example, AMVR for affine mode cannot be used if a         block is coded by IBC.     -   b. In one example, AMVR for affine mode may be used if a block         is coded by IBC, but the candidate MV/MVD/MVP precisions may be         different to those used for non-IBC coded affine-coded block.

Example 23

All the term “slice” in the document may be replaced by “tile group” or “tile”.

Example 24

In VPS/SPS/PPS/slice header/tile group header, a syntax element (e.g. no_amvr _constraint_flag) equal to 1 specifies that it is a requirement of bitstream conformance that both the syntax element to indicate whether AMVR is enabled (e.g. sps_amvr_enabled _flag) and the syntax element to indicate whether affine AMVR is enabled (e.g. sps_affine_avmr_enabled_flag) shall be equal to 0. The syntax element (e.g. no_amvr _constraint_flag) equal to 0 does not impose a constraint.

Example 25

In VPS/SPS/PPS/slice header/tile group header or other video data units, a syntax element (e.g. no_affine_amvr_constraint _flag) may be signalled.

-   -   a. In one example, no_affine_amvr_constraint _flag equal to 1         specifies that it is a requirement of bitstream conformance that         the syntax element to indicate whether affine AMVR is enabled         (e.g. sps_affine_avmr_enabled_flag) shall be equal to 0. The         syntax element (e.g. no_affine_amvr_constraint _flag) equal to 0         does not impose a constraint

Example 26

Multiple contexts may be utilized for coding the second syntax element which indicates the coarse motion precision (such as amvr_coarse _precision_flag).

-   -   a. In one example, two contexts may be utilized.     -   b. In one example, selection of contexts may depend on whether         the current block is affine coded or not.     -   c. In one example, for the first syntax, it may be coded with         only one context and also for the second syntax, it may be coded         with only one context.     -   d. In one example, for the first syntax, it may be coded with         only one context and also for the second syntax, it may be         bypass coded.     -   e. In one example, for the first syntax, it may be bypass coded         and also for the second syntax, it may be bypass coded.     -   f. In one example, for all syntax elements related to motion         vector precisions, they may be bypass coded.

Example 27

For example, only the first bin of the syntax element amvr_mode is coded with arithmetic coding context(s). All the following bins of amvr_mode are coded as bypass coding.

-   -   a. The above disclosed method may also be applied to other         syntax elements.     -   b. For example, only the first bin of the syntax element SE is         coded with arithmetic coding context(s). All the following bins         of SE are coded as bypass coding. SE may be         -   1) alf_ctb_flag         -   2) sao_merge_left_flag         -   3) sao_merge_up_flag         -   4) sao_type_idx_luma         -   5) sao_type_idx_chroma         -   6) split_cu_flag         -   7) split_qt_flag         -   8) mtt_split_cu_vertical_flag         -   9) mtt_split_cu_binary_flag         -   10) cu_skip_flag         -   11) pred_mode_ibc_flag         -   12) pred_mode_flag         -   13) intra_luma_ref_idx         -   14) intra_subpartitions_mode_flag         -   15) intra_subpartition_split_flag         -   16) intra_luma_mpm_flag         -   17) intra_chroma_pred_mode         -   18) merge_flag         -   19) inter_pred_idc         -   20) inter_affine_flag         -   21) cu_affine_type_flag         -   22) ref_idx_10         -   23) mvp_10_flag         -   24) ref_idx_11         -   25) mvp_11_flag         -   26) avmr_flag         -   27) amvr_precision_flag         -   28) gbi_idx         -   29) cu_cbf         -   30) cu_sbt_flag         -   31) cu_sbt_quad_flag         -   32) cu_sbt_horizontal_flag         -   33) cu_sbt_pos_flag         -   34) mmvd_flag         -   35) mmvd_merge_flag         -   36) mmvd_distance_idx         -   37) ciip_flag         -   38) ciip_luma_mpm_flag         -   39) merge_subblock_flag         -   40) merge_subblock_idx         -   41) merge_triangle_flag         -   42) merge_triangle_idx0         -   43) merge_triangle_idx1         -   44) merge_idx         -   45) abs_mvd_greater0_flag         -   46) abs_mvd_greater1_flag         -   47) tu_cbf_luma         -   48) tu_cbf_cb         -   49) tu_cbf_cr         -   50) cu_qp_delta_abs         -   51) transform_skip_flag         -   52) tu_mts_idx         -   53) last_sig_coeff_x_prefix         -   54) last_sig_coeff_y_prefix         -   55) coded_sub_block_flag         -   56) sig_coeff_flag         -   57) par_level_flag         -   58) abs_level_gt_1_flag         -   59) abs_level_gt3_flag     -   c. Alternatively, furthermore, if a syntax element SE is a         binary value (i.e., it could be only either equal to 0 or 1), it         may be context coded.         -   i. Alternatively, furthermore, if a syntax element SE is a             binary value (i.e., it could be only either equal to 0 or             1), it may be bypass coded.     -   d. Alternatively, furthermore, only 1 context may be used for         coding the first bin.

Example 28

The precision of motion vector prediction (MVP) or motion vector difference (MVD), or the reconstructed motion vector (MV) may be changed depending on the motion precision which may be signaled.

-   -   a. In one example MVP=MVP<<s if the original prediction of MVP         is lower (or not higher) than the target precision. s is an         integer, which may depend on the difference between the original         precision and the target precision.         -   iii. Alternatively, MVD=MVD<<s if the original precision of             MVD is lower (or not higher) than the target precision. s is             an integer, which may depend on the difference between the             original precision and the target precision.         -   iv. Alternatively, MV=MV<<s if the original precision of MV             is lower (or not higher) than the target precision. s is an             integer, which may depend on the difference between the             original precision and the target precision.             -   b. In one example MVP=Shift(MVP, s) if the original                 prediction of MVP is higher (or not lower) than the                 target precision. s is an integer, which may depend on                 the difference between the original precision and the                 target precision.         -   v. Alternatively, MVD=Shift(MVD, s) if the original             precision of MVD is higher (or not lower) than the target             precision. s is an integer, which may depend on the             difference between the original precision and the target             precision.         -   vi. Alternatively, MV=Shift(MV, s) if the original precision             of MV is higher (or not lower) than the target precision. s             is an integer, which may depend on the difference between             the original precision and the target precision.             -   c. In one example MVP=SatShift(MVP, s) if the original                 prediction of MVP is higher (or not lower) than the                 target precision. s is an integer, which may depend on                 the difference between the original precision and the                 target precision.         -   vii. Alternatively, MVD=SatShift(MVD, s) if the original             precision of MVD is higher (or not lower) than the target             precision. s is an integer, which may depend on the             difference between the original precision and the target             precision.         -   viii. Alternatively, MV=SatShift(MV, s) if the original             precision of MV is higher (or not lower) than the target             precision. s is an integer, which may depend on the             difference between the original precision and the target             precision.             -   d. The above methods disclosed may be applied when the                 current block is not coded with affine modes.             -   e. The above methods disclosed may be applied when the                 current block is coded with affine modes.

1. Embodiments

Highlighted parts show the modified specification.

1.1. Embodiment 1: Indication of Usage of Affine AMVR Mode

It may be signaled in SPS/PPS/VPS/APS/sequence header/picture header/tile group header, etc. al. This section presents the signalling in SPS.

1.1.1. SPS Syntax Table

seq_parameter_set_rbsp( ) { Descriptor  sps_seq_parameter_set_id ue(v) . . .  sps_amvr_enabled_flag u(1)  sps_bdof_enabled_flag u(1)  sps_affine_amvr_enabled_flag u(1)  sps_cclm_enabled_flag u(1)  sps_mts_intra_enabled_flag u(1)  sps_mts_inter_enabled_flag u(1)  sps_affine_enabled_flag u(1)  if( sps_affine_enabled_flag )   sps_affine_type_flag u(1)  sps_gbi_enabled_flag u(1)  sps_cpr_enabled_flag u(1) . . .  rbsp_trailing_bits( ) }

An alternative SPS syntax table is given as follows:

seq_parameter_set_rbsp( ) { Descriptor   sps_seq_parameter_set_id ue(v)   sps_amvr_enabled_flag u(1)   sps_bdof_enabled_flag u(1)   sps_cclm_enabled_flag u(1)   sps_mts_intra_enabled_flag u(1)   sps_mts_inter_enabled_flag u(1)   sps_affine_enabled_flag u(1)   if( sps_affine_enabled_flag ){     sps_affine_type_flag u(1)    sps_affine_amvr_enabled_flag u(1)  }   sps_gbi_enabled_flag u(1)   sps_cpr_enabled_flag u(1)   sps_ciip_enabled_flag u(1)   sps_triangle_enabled_flag u(1)   sps_ladf_enabled_flag u(1) . . .   rbsp_trailing_bits( ) }

Semantics:

sps_affine_amvr_enabled _flag equal to 1 specifies that adaptive motion vector difference resolution is used in motion vector coding of affine inter mode. amvr_enabled _flag equal to 0 specifies that adaptive motion vector difference resolution is not used in motion vector coding of affine inter mode.

1.2. Parsing Process of Affine AMVR Mode Information

Syntax of the affine AMVR mode information may reuse that for the AMVR mode information (applied to normal inter mode). Alternatively, different syntax elements may be utilized. Affine AMVR mode information may be conditionally signaled. Different embodiments below show some examples of the conditions.

1.2.1. Embodiment #1: CU Syntax Table

coding_unit( x0, y0, cbWidth, cbHeight, treeType ) { Descriptor  if( tile_group_type != I ) {   if( treeType != DUAL_TREE_CHROMA )    cu_skip_flag[ x0 ][ y0 ] ae(v)   if( cu_skip_flag[ x0 ][ y0 ] = = 0 )    pred_mode_flag ae(v)  }  if( CuPredMode[ x0 ][ y0 ] = = MODE_INTRA ) { . . .   }  } else if( treeType != DUAL_TREE_CHROMA ) { /* MODE_INTER */   if( cu_skip_flag[ x0 ][ y0 ] = = 0 )    merge_flag[ x0 ][ y0 ] ae(v)   if( merge_flag[ x0 ][ y0 ] ) {    merge_data( x0, y0, cbWidth, cbHeight )   } else {    if( tile_group_type = = B )     inter_pred_idc[ x0 ][ y0 ] ae(v)    if( sps_affine_enabled_flag && cbWidth >= 16 && cbHeight >= 16 ) {     inter_affine_flag[ x0 ][ y0 ] ae(v)     if( sps_affine_type_flag && inter_affine_flag[ x0 ][ y0 ] )      cu_affine_type_flag[ x0 ][ y0 ] ae(v)    }    if( inter_pred_idc[ x0 ][ y0 ] != PRED_L1 ) {     if( num_ref_idx_l0_active_minus1 > 0 )      ref_idx_l0[ x0 ][ y0 ] ae(v)     mvd_coding( x0, y0, 0, 0 )     if( MotionModelIdc[ x0 ][ y0 ] > 0 )      mvd_coding( x0, y0, 0, 1 )     if( MotionModelIdc[ x0 ][ y0 ] > 1 )      mvd_coding( x0, y0, 0, 2 )     mvp_l0_flag[ x0 ][ y0 ] ae(v)    } else {     MvdL0[ x0 ][ y0 ][ 0 ] = 0     MvdL0[ x0 ][ y0 ][ 1 ] = 0    }    if( inter_pred_idc[ x0 ][ y0 ] != PRED_L0 ) {     if( num_ref_idx_l1_active_minus1 > 0 )      ref_idx_l1[ x0 ][ y0 ] ae(v)     if( mvd_l1_zero_flag && inter_pred_idc[ x0 ][ y0 ] = = PRED_BI ) {      MvdL1[ x0 ][ y0 ][ 0 ] = 0      MvdL1[ x0 ][ y0 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 0 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 0 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 1 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 1 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 2 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 2 ][ 1 ] = 0     } else {      mvd_coding( x0, y0, 1, 0 )     if( MotionModelIdc[ x0 ][ y0 ] > 0 )      mvd_coding( x0, y0, 1, 1 )     if( MotionModelIdc[ x0 ][ y0 ] > 1 )      mvd_coding( x0, y0, 1, 2 )     mvp_l1_flag[ x0 ][ y0 ] ae(v)    } else {     MvdL1[ x0 ][ y0 ][ 0 ] = 0     MvdL1[ x0 ][ y0 ][ 1 ] = 0    }    if( ( sps_amvr_enabled_flag && inter_affine_flag = = 0 &&     ( MvdL0[ x0 ][ y0 ][ 0 ] != 0 | | MvdL0[ x0 ][ y0 ][ 1 ] != 0 | |     MvdL1[ x0 ][ y0 ][ 0 ] != 0 | | MvdL1[ x0 ][ y0 ][ 1 ] != 0 ) ) | |     ( sps_affine_amvr_enabled_flag && inter_affine_flag = = 1 &&     ( MvdCpL0[ x0 ][ y0 ][ 0 ][ 0 ] != 0 | | MvdCpL0[ x0 ][ y0 ][ 0 ][ 1 ] != 0 | |     MvdCpL1[ x0 ][ y0 ][ 0 ][ 0 ] != 0 | | MvdCpL1[ x0 ][ y0 ][ 0 ][ 1 ] != 0 | |     MvdCpL0[ x0 ][ y0 ][ 1 ][ 0 ] != 0 | | MvdCpL0[ x0 ][ y0 ][ 1 ][ 1 ] != 0 | |     MvdCpL1[ x0 ][ y0 ][ 1 ][ 0 ] != 0 | | MvdCpL1[ x0 ][ y0 ][ 1 ][ 1 ] != 0 | |     MvdCpL0[ x0 ][ y0 ][ 2 ][ 0 ] != 0 | | MvdCpL0[ x0 ][ y0 ][ 2 ][ 1 ] != 0 | |     MvdCpL1[ x0 ][ y0 ][ 2 ][ 0 ] != 0 | | MvdCpL1[ x0 ][ y0 ][ 2 ][ 1 ] != 0 ) ) ) {     if( !sps_cpr_enabled_flag | | !( inter_pred_idc[ x0 ][ y0 ] = = PRED_L0 &&  ref_idx_l0[ x0 ][ y0 ] = = num_ref_idx_l0_active_minus1 ) )      amvr_flag[ x0 ][ y0 ] ae(v)     if( amvr_flag[ x0 ][ y0 ] )      amvr_coarse_precisoin_flag[ x0 ][ y0 ] ae(v)    }    if( sps_gbi_enabled_flag && inter_pred_idc[ x0 ][ y0 ] = = PRED_BI &&     cbWidth * cbHeight >= 256 )     gbi_idx[ x0 ][ y0 ] ae(v)   }  }  if( !pcm_flag[ x0 ][ y0 ] ) {   if( CuPredMode[ x0 ][ y0 ] != MODE_INTRA && cu_skip_flag[ x0 ][ y0 ] = = 0 )    cu_cbf ae(v)   if( cu_cbf )    transform_tree( x0, y0, cbWidth, cbHeight, treeType )  } }

1.2.2. Embodiment 2: An Alternative CU Syntax Table Design

coding_unit( x0, y0, cbWidth, cbHeight, treeType ) { Descriptor  if( tile_group_type != I ) {   if( treeType != DUAL_TREE_CHROMA )    cu_skip_flag[ x0 ][ y0 ] ae(v)   if( cu_skip_flag[ x0 ][ y0 ] = = 0 )    pred_mode_flag ae(v)  }  if( CuPredModd[ x0 ][ y0 ] = = MODE_INTRA ) { . . .   }  } else if( treeType != DUAL_TREE_CHROMA ) { /* MODE_INTER */   if( cu_skip_flag[ x0 ][ y0 ] = = 0 )    merge_flag[ x0 ][ y0 ] ae(v)   if( merge_flag[ x0 ][ y0 ] ) {    merge_data( x0, y0, cbWidth, cbHeight )   } else {    if( tile_group_type = = B )     inter_pred_idc[ x0 ][ y0 ] ae(v)    if( sps_affine_enabled_flag && cbWidth >= 16 && cbHeight >= 16 ) {     inter_affine_flag[ x0 ][ y0 ] ae(v)     if( sps_affine_type_flag && inter_affine_flag[ x0 ][ y0 ] )      cu_affine_type_flag[ x0 ][ y0 ] ae(v)    }    if( inter_pred_idc[ x0 ][ y0 ] != PRED_L1 ) {     if( num_ref_idx_l0_active_minus1 > 0 )      ref_idx_l0[ x0 ][ y0 ] ae(v)     mvd_coding( x0, y0, 0, 0 )     if( MotionModelIdc[ x0 ][ y0 ] > 0 )      mvd_coding( x0, y0, 0, 1 )     if(MotionModelIdc[ x0 ][ y0 ] > 1 )      mvd_coding( x0, y0, 0, 2 )     mvp_l0_flag[ x0 ][ y0 ] ae(v)    } else {     MvdL0[ x0 ][ y0 ][ 0 ] = 0     MvdL0[ x0 ][ y0 ][ 1 ] = 0    }    if( inter_pred_idc[ x0 ][ y0 ] != PRED_L0 ) {     if( num_ref_idx_l1_active_minus1 > 0 )      ref_idx_l1[ x0 ][ y0 ] ae(v)     if( mvd_l1_zero_flag && inter_pred_idc[ x0 ][ y0 ] = = PRED_BI ) {      MvdL1[ x0 ][ y0 ][ 0 ] = 0      MvdL1[ x0 ][ y0 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 0 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 0 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 1 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 1 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 2 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 2 ][ 1 ] = 0     } else {      mvd_coding( x0, y0, 1, 0 )     if( MotionModelIdc[ x0 ][ y0 ] > 0 )      mvd_coding( x0, y0, 1, 1 )     if( MotionModelIdc[ x0 ][ y0 ] > 1 )      mvd_coding( x0, y0, 1, 2 )     mvp_l1_flag[ x0 ][ y0 ] ae(v)    } else {     MvdL1[ x0 ][ y0 ][ 0 ] = 0     MvdL1[ x0 ][ y0 ][ 1 ] = 0    }    if( ( sps_amvr_enabled_flag && inter_affine_flag = = 0 &&     ( MvdL0[ x0 ][ y0 ][ 0 ] != 0 | | MvdL0[ x0 ][ y0 ][ 1 ] != 0 | |     MvdL1[ x0 ][ y0 ][ 0 ] != 0 | | MvdL1[ x0 ][ y0 ][ 1 ] != 0 ) ) | |     ( sps_affine_amvr_enabled_flag && inter_affine_flag = = 1 &&     ( MvdCpL0[ x0 ][ y0 ][ 0 ] [ 0 ] != 0 | | MvdCpL0[ x0 ][ y0 ][ 0 ] [ 1 ] != 0 | |     MvdCpL1[ x0 ][ y0 ][ 0 ] [ 0 ] != 0 | | MvdCpL1[ x0 ][ y0 ][ 0 ] [ 1 ] != 0 ) ) ) {     if( !sps_cpr_enabled_flag | | !( inter_pred_idc[ x0 ][ y0 ] = = PRED_L0 &&  ref_idx_l0[ x0 ][ y0 ] = = num_ref_idx_l0_active_minus1 ) )      amvr_flag[ x0 ][ y0 ] ae(v)     if( amvr_flag[ x0 ][ y0 ] )      amvr_coarse_precisoin_flag[ x0 ][ y0 ] ae(v)    }    if( sps_gbi_enabled_flag && inter_pred_idc[ x0 ][ y0 ] = = PRED_BI &&     cbWidth * cbHeight >= 256 )     gbi_idx[ x0 ][ y0 ] ae(v)   }  }  if( !pcm_flag[ x0 ][ y0 ] ) {   if( CuPredMode[ x0 ][ y0 ] != MODE_INTRA && cu_skip_flag[ x0 ][ y0 ] = = 0 )    cu_cbf ae(v)   if( cu_cbf )    transform_tree( x0, y0, cbWidth, cbHeight, treeType )  } }

1.2.3. Embodiment 3: A ThirdCU Syntax Table Design

coding_unit( x0, y0, cbWidth, cbHeight, treeType ) { Descriptor  if( tile_group_type != I ) {   if( treeType != DUAL_TREE_CHROMA )    cu_skip_flag[ x0 ][ y0 ] ae(v)   if( cu_skip_flag[ x0 ][ y0 ] = = 0 )    pred_mode_flag ae(v)  }  if( CuPredMode[ x0 ][ y0 ] = = MODE_INTRA ) { . . .   }  } else if( treeType != DUAL_TREE_CHROMA ) { /* MODE_INTER */   if( cu_skip_flag[ x0 ][ y0 ] = = 0 )    merge_flag[ x0 ][ y0 ] ae(v)   if( merge_flag[ x0 ][ y0 ] ) {    merge_data( x0, y0, cbWidth, cbHeight )   } else {    if( tile_group_type = = B )     inter_pred_idc[ x0 ][ y0 ] ae(v)    if( sps_affine_enabled_flag && cbWidth >= 16 && cbHeight >= 16 ) {     inter_affine_flag[ x0 ][ y0 ] ae(v)     if( sps_affine_type_flag && inter_affine_flag[ x0 ][ y0 ] )      cu_affine_type_flag[ x0 ][ y0 ] ae(v)    }    if( inter_pred_idc[ x0 ][ y0 ] != PRED_L1 ) {     if( num_ref_idx_l0_active_minus1 > 0 )      ref_idx_l0[ x0 ][ y0 ] ae(v)     mvd_coding( x0, y0, 0, 0 )     if( MotionModelIdc[ x0 ][ y0 ] > 0 )      mvd_coding( x0, y0, 0, 1 )     if(MotionModelIdc[ x0 ][ y0 ] > 1 )      mvd_coding( x0, y0, 0, 2 )     mvp_l0_flag[ x0 ][ y0 ] ae(v)    } else {     MvdL0[ x0 ][ y0 ][ 0 ] = 0     MvdL0[ x0 ][ y0 ][ 1 ] = 0    }    if( inter_pred_idc[ x0 ][ y0 ] != PRED_L0 ) {     if( num_ref_idx_l1_active_minus1 > 0 )      ref_idx_l1[ x0 ][ y0 ] ae(v)     if( mvd_l1_zero_flag && inter_pred_idc[ x0 ][ y0 ] = = PRED_BI ) {      MvdL1[ x0 ][ y0 ][ 0 ] = 0      MvdL1[ x0 ][ y0 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 0 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 0 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 1 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 1 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 2 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 2 ][ 1 ] = 0     } else {      mvd_coding( x0, y0, 1, 0 )     if( MotionModelIdc[ x0 ][ y0 ] > 0 )      mvd_coding( x0, y0, 1, 1 )     if( MotionModelIdc[ x0 ][ y0 ] > 1 )      mvd_coding( x0, y0, 1, 2 )     mvp_l1_flag[ x0 ][ y0 ] ae(v)    } else {     MvdL1[ x0 ][ y0 ][ 0 ] = 0     MvdL1[ x0 ][ y0 ][ 1 ] = 0    }    if( ( sps_amvr_enabled_flag && inte_affine_flag = = 0 &&     ( MvdL0[ x0 ][ y0 ][ 0 ] != 0 | | MvdL0[ x0 ][ y0 ][ 1 ] != 0 | |     MvdL1[ x0 ][ y0 ][ 0 ] != 0 | | MvdL1[ x0 ][ y0 ][ 1 ] != 0 ) ) | |     ( sps_affine_amvr_enabled_flag && inter_affine_flag = = 1) ) {     if( !sps_cpr_enabled_flag | | !( inter_pred_idc[ x0 ][ y0 ] = = PRED_L0 &&  ref_idx_l0[ x0 ][ y0 ] = = num_ref_idx_l0_active_minus1 ) )      amvr_flag[ x0 ][ y0 ] ae(v)     if( amvr_flag[ x0 ][ y0 ] )      amvr_coarse_precisoin_flag[ x0 ][ y0 ] ae(v)    }    if( sps_gbi_enabled_flag && inter_pred_idc[ x0 ][ y0 ] = = PRED_BI &&     cbWidth * cbHeight >= 256 )     gbi_idx[ x0 ][ y0 ] ae(v)   }  }  if( !pcm_flag[ x0 ][ y0 ] ) {   if( CuPredMode[ x0 ][ y0 ] != MODE_INTRA && cu_skip_flag[ x0 ][ y0 ] = = 0 )    cu_cbf ae(v)   if( cu_cbf )    transform_tree( x0, y0, cbWidth, cbHeight, treeType )  } }

1.2.4. Embodiment 4: Syntax Table Design with Different Syntax for AMVR and Affine AMVR Mode

coding_unit( x0, y0, cbWidth, cbHeight, treeType) {  if( tile_group_type != I ) {   if( treeType != DUAL_TREE_CHROMA )    cu_skip_flag[ x0 ][ y0 ]   if( cu_skip_flag[ x0 ][ y0 ] = = 0 )    pred_mode_flag  }  if( CuPredMode[ x0 ][ y0 ] = = MODE_INTRA ) { . . .   }  } else if( treeType != DUAL_TREE_CHROMA ) { /* MODE_INTER  */   if( cu_skip_flag[ x0 ][ y0 ] = = 0 )    merge_flag[ x0 ][ y0 ]   if( merge_flag[ x0 ][ y0 ] ) {    merge_data( x0, y0, cbWidth, cbHeight )   } else {    if( tile_group_type = = B )     inter_pred_idc[ x0 ][ y0 ]    if( sps_affine_enabled_flag && cbWidth >= 16 && cbHeight >= 16 ) {     inter_affine_flag[ x0 ][ y0 ]     if( sps_affine_type_flag && inter_affine_flag[ x0 ][ y0 ] )      cu_affine_type_flag[ x0 ][ y0 ]    }    if( inter_pred_idc[ x0 ][ y0 ] != PRED_L1 ) {     if( num_ref_idx_l0_active_minus1 > 0 )      ref_idx_l0[ x0 ][ y0 ]     mvd_coding( x0, y0, 0, 0 )     if( MotionModelIdc[ x0 ][ y0 ] > 0 )      mvd_coding( x0, y0, 0, 1 )     if( MotionModelIdc[ x0 ][ y0 ] > 1 )      mvd_coding( x0, y0, 0, 2 )     mvp_l0_flag[ x0 ][ y0 ]    } else {     MvdL0[ x0 ][ y0 ][ 0 ] = 0     MvdL0[ x0 ][ y0 ][ 1 ] = 0    }    if( inter_pred_idc[ x0 ][ y0 ] != PRED_L0 ) {     if( num_ref_idx_l1_active_minus1 > 0 )      ref_idx_l1[ x0 ][ y0 ]     if( mvd_l1_zero_flag && inter_pred_idc[ x0 ][ y0 ] = = PRED_BI ) {      MvdL1[ x0 ][ y0 ][ 0 ] = 0      MvdL1[ x0 ][ y0 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 0 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 0 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 1 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 1 ][ 1 ] = 0      MvdCpL1[ x0 ][ y0 ][ 2 ][ 0 ] = 0      MvdCpL1[ x0 ][ y0 ][ 2 ][ 1 ] = 0     } else {      mvd_coding( x0, y0, 1, 0 )     if( MotionModelIdc[ x0 ][ y0 ] > 0 )      mvd_coding( x0, y0, 1, 1 )     if( MotionModelIdc[ x0 ][ y0 ] > 1 )      mvd_coding( x0, y0, 1, 2 )     mvp_l1_flag[ x0 ][ y0 ]    } else {     MvdL1[ x0 ][ y0 ][ 0 ] = 0     MvdL1[ x0 ][ y0 ][ 1 ] = 0    }    if(sps_amvr_enabled_flag && inter_affine_flag = = 0 &&     ( MvdL0[ x0 ][ y0 ][ 0 ] != 0 | | MvdL0[ x0 ][ y0 ][ 1 ] != 0 | |     MvdL1[ x0 ][ y0 ][ 0 ] != 0 | | MvdL1[ x0 ][ y0 ][ 1 ] != 0 )) {     if( !sps_cpr_enabled_flag | | !( inter_pred_idc[ x0 ][ y0 ] = = PRED_L0 &&  ref_idx_l0[ x0 ][ y0 ] = = num_ref_idx_l0_active_minus1 ) )      amvr_flag[ x0 ][ y0 ]     if( amvr_flag[ x0 ][ y0 ] )      amvr_coarse_precisoin_flag[ x0 ][ y0 ]    } else if (conditionsA) {     if(conditionsB)      affine_amvr_flag[ x0 ][ y0 ]     if( amvr_flag[ x0 ][ y0 ] )      affine_amvr_coarse_precisoin_flag[ x0 ][ y0 ]    }    if( sps_gbi_enabled_flag && inter_pred_idc[ x0 ][ y0 ] = = PRED_BI &&     cbWidth * cbHeight >= 256 )     gbi_idx[ x0 ][ y0 ]   }  }  if( !pcm_flag[ x0 ][ y0 ] ) {   if( CuPredMode[ x0 ][ y0 ] != MODE_INTRA && cu_skip_flag[ x0 ][ y0 ] = = 0 )    cu_cbf   if( cu_cbf )    transform_tree( x0, y0, cbWidth, cbHeight, treeType )  } }

-   -   In one example, conditionsA is defined as follows:         -   (sps_affine_amvr_enabled _flag && inter_affine _flag==1 &&             -   (MvdCpL0[x0][y0][0][0]!=0∥         -   MvdCpL0[x0][y0][0] [1] !=0∥             -   MvdCpL1[x0][y0][0][0]!=0∥         -   MvdCpL1[x0][y0][0] [1] !=0∥             -   MvdCpL0[x0][y0][1] [0] !=0∥         -   MvdCpL0[x0][y0][1] [1] !=0∥             -   MvdCpL1[x0][y0][1] [0] !=0∥         -   MvdCpL1[x0][y0][1] [1] !=0∥             -   MvdCpL0[x0][y0][2] [0] !=0∥         -   MvdCpL0[x0][y0][2] [1] !=0∥             -   MvdCpL1[x0][y0][2][0]!=0∥         -   MvdCpL1[x0][y0][2] [1] !=0))

Alternatively, conditionsA is defined as follows:

-   -   (sps_affine_amvr_enabled _flag && inter_affine _flag==1 &&         -   (MvdCpL0[x0][y0][0][0]!=0∥     -   MvdCpL0[x0][y0][0] [1] !=0∥         -   MvdCpL1[x0][y0][0][0]!=0∥     -   MvdCpL1[x0][y0][0] [1] !=0∥)

Alternatively, conditionsA is defined as follows:

-   -   (sps_affine_amvr_enabled _flag && inter_affine _flag==1 &&         -   (MvdCpLX[x0][y0][0] [0] !=0∥     -   MvdCpLX[x0][y0][0] [1] !=0)         wherein Xis being 0 or 1.

Alternatively, conditionsA is defined as follows:

-   -   (sps_affine_amvr_enabled _flag && inter_affine _flag==1)

In one example, conditionsB is defined as follows:

-   -   !sps_cpr_enabled_flag∥!(inter_pred _idc[x0][y0]==PRED_L0 &&         -   ref_idx _10[x0][y0]==num_ref_idx _10_active_minus1)

Alternatively, conditionsB is defined as follows:

-   -   !sps_cpr_enabled_flag∥!(pred_mode[x0][y0]==CPR).

Alternatively, conditionsB is defined as follows:

-   -   !sps_ibc _enabled_flag∥!(pred_mode[x0][y0]==IBC).

When different syntax elements are utilized to code AMVR or Affine AMVR, the context modeling and/or contexts used for the embodiments in 5.5 which are applied to Affine AMVR may be applied accordingly.

1.2.5. Semantics

amvr_flag[x0][y0] specifies the resolution of motion vector difference. The array indices x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture. amvr_flag[x0][y0] equal to 0 specifies that the resolution of the motion vector difference is ¼ of a luma sample. amvr_flag[x0][y0] equal to 1 specifies that the resolution of the motion vector difference is further specified by amvr_coarse _precisoin_flag[x0][y0].

When amvr_flag[x0][y0] is not present, it is inferred as follows:

-   -   If sps_cpr_enabled_flag is equal to 1, amvr_flag[x0] [y0] is         inferred to be equal to 1.     -   Otherwise (sps_cpr_enabled_flag is equal to 0), amvr_flag[x0 II         y0] is inferred to be equal to 0.

amvr_coarse _precisoin_flag[x0][y0] equal to 1 specifies that the resolution of the motion vector difference is four luma samples when inter_affine _flag is equal to 0, and 1 luma samples when inter_affine _flag is equal to 1. The array indices x0, y0 specify the location (x0, y0) of the top-left luma sample of the considered coding block relative to the top-left luma sample of the picture.

When amvr_coarse _precisoin_flag[x0][y0] is not present, it is inferred to be equal to 0. If inter_affine _flag[x0][y0] is equal to 0, the variable MvShift is set equal to (amvr_flag[x0][y0]+amvr_coarse_precisoin _flag[x0][y0])<<1 and the variables MvdL0[x0][y0][0], MvdL0[x0][y0][1], MvdL1[x0][y0][0], MvdL1[x0][y0][1] are modified as follows:

MvdL0[x0][y0][0]=MvdL0[x0][y0][0]<<(MvShift+2)  (7-70)

MvdL0[x0][y0][1]=MvdL0[x0][y0][1]<<(MvShift+2)  (7-71)

MvdL1[x0][y0][0]=MvdL1[x0][y0][0]<<(MvShift+2)  (7-72)

MvdL1[x0][y0][1]=MvdL1[x0][y0][1]<<(MvShift+2)  (7-73)

If inter_affine_flag[x0][y0] is equal to 1, the variable MvShift is set equal to (amvr_coarse _precisoin_flag? (amvr_coarse_precisoin _flag<<1): (−(amvr_flag<<1))) and the variables MvdCpL0[x0][y0][0][0], MvdCpL0[x0][y0][0][1], MvdCpL0[x0][y0][1][0], MvdCpL0[x0][y0][1][1], MvdCpL0[x0][y0][2][0], MvdCpL0[x0][y0][2][1] are modified as follows:

MvdCpL0[x0][y0][0][0]=MvdCpL0[x0][y0][0][0]<<(MvShift+2)  (7-73)

MvdCpL1[x0][y0][0][1]=MvdCpL1[x0][y0][0][1]<<(MvShift+2)  (7-67)

MvdCpL0[x0][y0][1][0]=MvdCpL0[x0][y0][1][0]<<(MvShift+2)  (7-66)

MvdCpL1[x0][y0][1][1]=MvdCpL1[x0][y0][1][1]<<(MvShift+2)  (7-67)

MvdCpL0[x0][y0][2][0]=MvdCpL0[x0][y0][2][0]<<(MvShift+2)  (7-66)

MvdCpL1[x0][y0][2][1]=MvdCpL1[x0][y0][2][1]<<(MvShift+2)  (7-67)

Alternatively, if inter_affine _flag[x0][y0] is equal to 1, the variable MvShift is set equal to (affine_amvr_coarse _precisoin_flag? (affine_amvr_coarse _precisoin_flag<<1):(−(affine_amvr_flag<<1))).

1.3. Rounding Process for Motion Vectors

The rounding process is modified that when the given rightShift value is equal to 0 (which happens for 1/16-pel precision), the rounding offset is set to 0 instead of (1<<(rightShift−1)).

For example, the sub-clause of rounding process for MVs is modified as follows: Inputs to this process are:

-   -   the motion vector mvX,     -   the right shift parameter rightShift for rounding,     -   the left shift parameter leftShift for resolution increase.

Output of this process is the rounded motion vector mvX.

For the rounding of mvX, the following applies:

offset=(rightShift==0)?0:(1<<(rightShift−1))  (8-371)

mvX[0]=(mvX[0]>=0?(mvX[0]+offset)>>rightShift:

((−mvX[0]+offset)>>rightShift))<<leftShift   (8-372)

mvX[1]=(mvX[1]>=0?(mvX[1]+offset)>>rightShift:

((−mvX[1]+offset)>>rightShift))<<leftShift  (8-373)

1.4. Decoding Process

The rounding process invoked in the affine motion vector derivation process are performed with the input of (MvShift+2) instead of being fixed to be 2.

Derivation Process for Luma Affine Control Point Motion Vector Predictors

Inputs to this process are:

-   -   a luma location (xCb, yCb) of the top-left sample of the current         luma coding block relative to the top-left luma sample of the         current picture,     -   two variables cbWidth and cbHeight specifying the width and the         height of the current luma coding block,     -   the reference index of the current coding unit refIdxLX, with X         being 0 or 1,     -   the number of control point motion vectors numCpMv.

Output of this process are the luma affine control point motion vector predictors mvpCpLX[cpIdx] with X being 0 or 1, and cpIdx=0 . . . numCpMv−1.

For the derivation of the control point motion vectors predictor candidate list, cpMvpListLX with X being 0 or 1, the following ordered steps apply:

The number of control point motion vector predictor candidates in the list numCpMvpCandLX is set equal to 0.

The variables availableFlagA and availableFlagB are both set equal to FALSE.

. . .

The rounding process for motion vectors as specified in clause 8.4.2.14 is invoked with mvX set equal to cpMvpLX[cpIdx], rightShift set equal to (MvShift+2), and leftShift set equal to (MvShift+2) as inputs and the rounded cpMvpLX[cpIdx] with cpIdx=0 . . . numCpMv−1 as output.

. . .

The variable availableFlagA is set equal to TRUE

The derivation process for luma affine control point motion vectors from a neighbouring block as specified in clause 8.4.4.5 is invoked with the luma coding block location (xCb, yCb), the luma coding block width and height (cbWidth, cbHeight), the neighbouring luma coding block location (xNb, yNb), the neighbouring luma coding block width and height (nbW, nbH), and the number of control point motion vectors numCpMv as input, the control point motion vector predictor candidates cpMvpLY[cpIdx] with cpIdx=0 . . . numCpMv−1 as output.

The rounding process for motion vectors as specified in clause 8.4.2.14 is invoked with mvX set equal to cpMvpLY[cpIdx], rightShift set equal to (MvShift+2), and leftShift set equal to (MvShift+2) as inputs and the rounded cpMvpLY[cpIdx] with cpIdx=0 . . . numCpMv−1 as output.

. . .

The derivation process for luma affine control point motion vectors from a neighbouring block as specified in clause 8.4.4.5 is invoked with the luma coding block location (xCb, yCb), the luma coding block width and height (cbWidth, cbHeight), the neighbouring luma coding block location (xNb, yNb), the neighbouring luma coding block width and height (nbW, nbH), and the number of control point motion vectors numCpMv as input, the control point motion vector predictor candidates cpMvpLX[cpIdx] with cpIdx=0 . . . numCpMv−1 as output.

The rounding process for motion vectors as specified in clause 8.4.2.14 is invoked with mvX set equal to cpMvpLX[cpIdx], rightShift set equal to (MvShift+2), and leftShift set equal to (MvShift+2) as inputs and the rounded cpMvpLX[cpIdx] with cpIdx=0 . . . numCpMv−1 as output.

The following assignments are made:

cpMvpListLX[numCpMvpCandLX][0]=cpMvpLX[0]  (8-618)

cpMvpListLX[numCpMvpCandLX][1]=cpMvpLX[1]  (8-619)

cpMvpListLX[numCpMvpCandLX][2]=cpMvpLX[2]  (8-620)

numCpMvpCandLX=numCpMvpCandLX+1  (8-621)

Otherwise if PredFlagLY[xNbBk][yNbBk] (with Y=!X) is equal to 1 and DiffPicOrderCnt(RefPicListY[RefIdxLY[xNbBk][yNbBk]], RefPicListX[refIdxLX]) is equal to 0, the following applies:

The variable availableFlagB is set equal to TRUE

The derivation process for luma affine control point motion vectors from a neighbouring block as specified in clause 8.4.4.5 is invoked with the luma coding block location (xCb, yCb), the luma coding block width and height (cbWidth, cbHeight), the neighbouring luma coding block location (xNb, yNb), the neighbouring luma coding block width and height (nbW, nbH), and the number of control point motion vectors numCpMv as input, the control point motion vector predictor candidates cpMvpLY[cpIdx] with cpIdx=0 . . . numCpMv−1 as output.

The rounding process for motion vectors as specified in clause 8.4.2.14 is invoked with mvX set equal to cpMvpLY[cpIdx], rightShift set equal to (MvShift+2), and leftShift set equal to (MvShift+2) as inputs and the rounded cpMvpLY[cpIdx] with cpIdx=0 . . . numCpMv−1 as output.

The following assignments are made:

cpMvpListLX[numCpMvpCandLX][0]=cpMvpLY[0]  (8-622)

cpMvpListLX[numCpMvpCandLX][1]=cpMvpLY[1]  (8-623)

cpMvpListLX[numCpMvpCandLX][2]=cpMvpLY[2]  (8-624)

numCpMvpCandLX=numCpMvpCandLX+1  (8-625)

When numCpMvpCandLX is less than 2, the following applies

The derivation process for constructed affine control point motion vector prediction candidate as specified in clause 8.4.4.8 is invoked with the luma coding block location (xCb, yCb), the luma coding block width cbWidth, the luma coding block height cbHeight, and the reference index of the current coding unit refIdxLX as inputs, and the availability flag availableConsFlagLX, the availability flags availableFlagLX[cpIdx] and cpMvpLX[cpIdx] with cpIdx=0 . . . numCpMv−1 as outputs.

When availableConsFlagLX is equal to 1, and numCpMvpCandLX is equal to 0, the following assignments are made:

cpMvpListLX[numCpMvpCandLX][0]=cpMvpLX[0]  (8-626)

cpMvpListLX[numCpMvpCandLX][1]=cpMvpLX[1]  (8-627)

cpMvpListLX[numCpMvpCandLX][2]=cpMvpLX[2]  (8-628)

numCpMvpCandLX=numCpMvpCandLX+1  (8-629)

The following applies for cpIdx=0 . . . numCpMv−1:

When numCpMvpCandLX is less than 2 and availableFlagLX[cpIdx] is equal to 1, the following assignments are made:

cpMvpListLX[numCpMvpCandLX][0]=cpMvpLX[cpIdx]  (8-630)

cpMvpListLX[numCpMvpCandLX][1]=cpMvpLX[cpIdx]  (8-631)

cpMvpListLX[numCpMvpCandLX][2]=cpMvpLX[cpIdx]  (8-632)

numCpMvpCandLX=numCpMvpCandLX+1(8-633)

When numCpMvpCandLX is less than 2, the following applies:

The derivation process for temporal luma motion vector prediction as specified in clause 8.4.2.11 is with the luma coding block location (xCb, yCb), the luma coding block width cbWidth, the luma coding block height cbHeight and refIdxLX as inputs, and with the output being the availability flag availableFlagLXCol and the temporal motion vector predictor mvLXCol.

When availableFlagLXCol is equal to 1, the following applies: The rounding process for motion vectors as specified in clause 8.4.2.14 is invoked the with mvX set equal to mvLXCol, rightShift set equal to (MvShift+2), and leftShift set equal to (MvShift+2) as inputs and the rounded mvLXCol as output.

The following assignments are made:

cpMvpListLX[numCpMvpCandLX][0]=mvLXCol  (8-634)

cpMvpListLX[numCpMvpCandLX][1]=mvLXCol  (8-635)

cpMvpListLX[numCpMvpCandLX][2]=mvLXCol  (8-636)

numCpMvpCandLX=numCpMvpCandLX+1  (8-637)

When numCpMvpCandLX is less than 2, the following is repeated until numCpMvpCandLX is equal to 2, with mvZero[0] and mvZero[1] both being equal to 0:

cpMvpListLX[numCpMvpCandLX][0]=mvZero  (8-638)

cpMvpListLX[numCpMvpCandLX][1]=mvZero  (8-639)

cpMvpListLX[numCpMvpCandLX][2]=mvZero  (8-640)

numCpMvpCandLX=numCpMvpCandLX+1  (8-641)

The affine control point motion vector predictor cpMvpLX with X being 0 or 1 is derived as follows:

cpMvpLX=cpMvpListLX[mvp_1X_flag[xCb][yCb]]  (8-642)

Derivation Process for Constructed Affine Control Point Motion Vector Prediction Candidates

Inputs to this process are:

-   -   a luma location (xCb, yCb) specifying the top-left sample of the         current luma coding block relative to the top-left luma sample         of the current picture,     -   two variables cbWidth and cbHeight specifying the width and the         height of the current luma coding block,     -   the reference index of the current prediction unit partition         refIdxLX, with X being 0 or 1,

Output of this process are:

-   -   the availability flag of the constructed affine control point         motion vector prediction candidiates availableConsFlagLX with X         being 0 or 1,     -   the availability flags availableFlagLX[cpIdx] with cpIdx=0 . . .         2 and X being 0 or 1,     -   the constructed affine control point motion vector prediction         candidiates cpMvLX[cpIdx] with cpIdx=0 . . . numCpMv−1 and X         being 0 or 1.

The first (top-left) control point motion vector cpMvLX[0] and the availability flag availableFlagLX[0] are derived in the following ordered steps:

The sample locations (xNbB2, yNbB2), (xNbB3, yNbB3) and (xNbA2, yNbA2) are set equal to (xCb−1, yCb−1), (xCb, yCb−1) and (xCb−1, yCb), respectively.

The availability flag availableFlagLX[0] is set equal to 0 and both components of cpMvLX[0] are set equal to 0.

The following applies for (xNbTL, yNbTL) withTL being replaced by B2, B3, and A2:

The availability derivation process for a coding block as specified in clause is invoked with the luma coding block location (xCb, yCb), the luma coding block width cbWidth, the luma coding block height cbHeight, the luma location (xNbY, yNbY) set equal to (xNbTL, yNbTL) as inputs, and the output is assigned to the coding block availability flag availableTL.

When availableTL is equal to TRUE and availableFlagLX[0] is equal to 0, the following applies:

If PredFlagLX[xNbTL][yNbTL] is equal to 1, and

DiffPicOrderCnt(RefPicListX[RefIdxLX[xNbTL][yNbTL]], RefPicListX[refIdxLX]) is equal to 0, and the reference picture corresponding to RefIdxLX[xNbTL][yNbTL] is not the current picture, availableFlagLX[0] is set equal to 1 and the following assignments are made:

cpMvLX[0]=MvLX[xNbTL][yNbTL]  (8-643)

Otherwise, when PredFlagLY[xNbTL][yNbTL] (with Y=!X) is equal to 1 and DiffPicOrderCnt(RefPicListY[RefIdxLY[xNbTL][yNbTL]], RefPicListX[refIdxLX]) is equal to 0, and the reference picture corresponding to RefIdxLY[xNbTL][yNbTL] is not the current picture, availableFlagLX[0] is set equal to 1 and the following assignments are made:

cpMvLX[0]=MvLY[xNbTL][yNbTL]  (8-644)

When availableFlagLX[0] is equal to 1, the rounding process for motion vectors as specified in clause 8.4.2.14 is invoked with mvX set equal to cpMvLX[0], rightShift set equal to (MvShift+2), and leftShift set equal to (MvShift+2) as inputs and the rounded cpMvLX[0] as output.

The second (top-right) control point motion vector cpMvLX[1] and the availability flag availableFlagLX[1] are derived in the following ordered steps:

The sample locations (xNbB1, yNbB1) and (xNbB0, yNbB0) are set equal to (xCb+cbWidth−1, yCb−1) and (xCb+cbWidth, yCb−1), respectively.

The availability flag availableFlagLX[1] is set equal to 0 and both components of cpMvLX[1] are set equal to 0.

The following applies for (xNbTR, yNbTR) withTR being replaced by B1 and B0:

The availability derivation process for a coding block as specified in clause 6.4.X is invoked with the luma coding block location (xCb, yCb), the luma coding block width cbWidth, the luma coding block height cbHeight, the luma location (xNbY, yNbY) set equal to (xNbTR, yNbTR) as inputs, and the output is assigned to the coding block availability flag availableTR.

When availableTR is equal to TRUE and availableFlagLX[1] is equal to 0, the following applies:

If PredFlagLX[xNbTR][yNbTR] is equal to 1, and

DiffPicOrderCnt(RefPicListX[RefIdxLX[xNbTR][yNbTR]], RefPicListX[refIdxLX]) is equal to 0, and the reference picture corresponding to RefIdxLX[xNbTR][yNbTR] is not the current picture, availableFlagLX[1] is set equal to 1 and the following assignments are made:

cpMvLX[1]=MvLX[xNbTR][yNbTR]  (8-645)

Otherwise, when PredFlagLY[xNbTR][yNbTR] (with Y=!X) is equal to 1 and

DiffPicOrderCnt(RefPicListY[RefIdxLY[xNbTR][yNbTR]], RefPicListX[refIdxLX]) is equal to 0, and the reference picture corresponding to RefIdxLY[xNbTR][yNbTR] is not the current picture, availableFlagLX[1] is set equal to 1 and the following assignments are made:

cpMvLX[1]=MvLY[xNbTR][yNbTR]  (8-646)

When availableFlagLX[1] is equal to 1, the rounding process for motion vectors as specified in clause 8.4.2.14 is invoked with mvX set equal to cpMvLX[1], rightShift set equal to (MvShift+2), and leftShift set equal to (MvShift+2) as inputs and the rounded cpMvLX[1] as output.

The third (bottom-left) control point motion vector cpMvLX[2] and the availability flag availableFlagLX[2] are derived in the following ordered steps:

The sample locations (xNbA1, yNbA1) and (xNbA0, yNbA0) are set equal to (xCb−1, yCb+cbHeight−1) and (xCb−1, yCb+cbHeight), respectively.

The availability flag availableFlagLX[2] is set equal to 0 and both components of cpMvLX[2] are set equal to 0.

The following applies for (xNbBL, yNbBL) with BL being replaced by A1 and A0:

The availability derivation process for a coding block as specified in clause 6.4.X invoked with the luma coding block location (xCb, yCb), the luma coding block width cbWidth, the luma coding block height cbHeight, the luma location (xNbY, yNbY) set equal to (xNbBL, yNbBL) as inputs, and the output is assigned to the coding block availability flag availableBL.

When availableBL is equal to TRUE and availableFlagLX[2] is equal to 0, the following applies:

If PredFlagLX[xNbBL][yNbBL] is equal to 1, and DiffPicOrderCnt(RefPicListX[RefIdxLX[xNbBL][yNbBL]], RefPicListX[refIdxLX]) is equal to 0, and the reference picture corresponding to RefIdxLY[xNbBL][yNbBL] is not the current picture, availableFlagLX[2] is set equal to 1 and the following assignments are made:

cpMvLX[2]=MvLX[xNbBL][yNbBL]  (8-647)

Otherwise, when PredFlagLY[xNbBL][yNbBL] (with Y=!X) is equal to 1 and DiffPicOrderCnt(RefPicListY[RefIdxLY[xNbBL][yNbBL]], RefPicListX[refIdxLX]) is equal to 0, and the reference picture corresponding to RefIdxLY[xNbBL][yNbBL] is not the current picture, availableFlagLX[2] is set equal to 1 and the following assignments are made:

cpMvLX[2]=MvLY[xNbBL][yNbBL]  (8-648)

When availableFlagLX[2] is equal to 1, the rounding process for motion vectors as specified in clause 8.4.2.14 is invoked with mvX set equal to cpMvLX[2], rightShift set equal to (MvShift+2), and leftShift set equal to (MvShift+2) as inputs and the rounded cpMvLX[2] as output.

1.5. Context Modeling

Assignment of ctxInc to syntax elements with context coded bins:

binIdx Syntax element 0 1 2 3 4 >=5 amvr_flag[ ][ ] 0, 1, 2 na na na na na (clause 9.5.4.2.2, when inter_affine_ flag[ ][ ] is equal to 0) amvr_coarse_ 0 na na na na na precisoin_flag [ ][ ]

Specification of ctxInc using left and above syntax elements:

In one example, context increasement offset ctxInc=(condL && availableL)+

(condA && availableA)+ctxSetIdx*3.

Alternatively, ctxInc=((condL && availableL)∥(condA && availableA))+ctxSetIdx*3.

ctxInc=(condL && availableL)+M*(condA && availableA)+ctxSetIdx*3. (e.g., M=2)

ctxInc=M*(condL && availableL)+(condA && availableA)+ctxSetIdx*3. (e.g., M=2)

Syntax element condL condA ctxSetIdx e cu_skip_flag[ xNbL ][ yNbL ] cu_skip_flag[ xNbA ][ yNbA ] 0 e !inter_affine_flag[ x0 ][ y0 ] !inter_affine_flag[ x0 ][ y0 ] 0 && && amvr_flag[ xNbL ][ yNbL ] amvr_flag[ xNbA ][ yNbA ]

Values of initValue for ctxIdx of amvr_flag:

Different contexts are used when current block is affine or non-affine.

ctxIdx of amvr_flag when ctxIdx of amvr_flag when Initialization inter_affine_flag is equal to 0 inter_affine_flag is equal to 1 variable 0 1 2 3 initValue xx xx xx xx

Alternatively,

ctxIdx of amvr_flag when ctxIdx of amvr_flag when Initialization inter_affine_flag is equal to 0 inter_affine_flag is equal to 1 variable 0 1 initValue xx xx

Alternatively, same contexts may be used when current block is affine or non-affine.

ctxIdx of amvr_flag when ctxIdx of amvr_flag when Initialization inter_affine_flag is equal to 0 inter_affine_flag is equal to 1 variable 0 0 initValue xx xx

Alternatively, amvr_flag is bypass coded.

Values of initValue for ctxIdx of amvr_coarse_precisoin _flag:

Different contexts are used when current block is affine or non-affine.

ctxIdx of ctxIdx of amvr_coarse_precisoin_flag amvr_coarse_precisoin_flag when Initialization when inter_affine_flag is equal to 0 inter_affine_flag is equal to 1 variable 0 0 initValue xxx xx

Alternatively,

ctxIdx of ctxIdx of amvr_coarse_precisoin_flag amvr_coarse_precisoin_flag when Initialization when inter_affine_flag is equal to 0 inter_affine_flag is equal to 1 variable 0 1 initValue xxx xx

Alternatively, same contexts may be used when current block is affine or non-affine.

Initialization ctxIdx of amvr_coarse_precisoin_flag variable 0 initValue xxx

Alternatively, amvr_coarse_precisoin _flag is bypass coded.

The examples described above may be incorporated in the context of the method described below, e.g., methods 2510 to 2540, which may be implemented at a video decoder or a video encoder.

FIGS. 25A to 25D show flowcharts of exemplary methods for video processing. The method 2510 as shown in FIG. 25A includes, at step 2512, determining that a conversion between a current video block of a video and a coded representation of the current video block is based on a non-affine inter AMVR mode. The method 2510 further includes, at step 2514, performing the conversion based on the determining. In some implementations, the coded representation of the current video block is based on a context based coding, and wherein a context used for coding the current video block is modeled without using an affine AMVR mode information of a neighboring block during the conversion

The method 2520 as shown in FIG. 25B includes, at step 2522, determining that a conversion between a current video block of a video and a coded representation of the current video block is based on an affine adaptive motion vector resolution (affine AMVR) mode. The method 2520 further includes, at step 2524, performing the conversion based on the determining. In some implementations, the coded representation of the current video block is based on a context based coding, and wherein a variable controls two probability updating speeds for a context.

The method 2530 as shown in FIG. 25C includes, at step 2532, determining that a conversion between a current video block of a video and a coded representation of the current video block is based on an affine AMVR mode. The method 2530 further includes, at step 2534, performing the conversion based on the determining. In some implementations, the coded representation of the current video block is based on a context based coding, and wherein a context used for coding the current video block is modeled using a coding information of a neighboring block for which an AMVR mode of both affine inter mode and normal inter mode is used during the conversion.

The method 2540 as shown in FIG. 25D includes, at step 2542, determining, for a conversion between a current video block of a video and a coded representation of the current video block, a usage of multiple contexts for the conversion. The method 2540 further includes, at step 2544, performing the conversion based on the determining. In some implementations, the multiple contexts are utilized for coding a syntax element indicating a coarse motion precision.

The method 2550 as shown in FIG. 25E includes, at step 2552, making a determination, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use a symmetric motion vector difference (SMVD) mode based on a currently selected best mode for the conversion. The method 2554 further includes, performing the conversion based on the determining.

The method 2560 as shown in FIG. 25F includes, at step 2562, making a determining, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use an affine SMVD mode based on a currently selected best mode for the conversion. The method 2564 further includes, performing the conversion based on the determining.

5. Example Implementations of the Disclosed Technology

FIG. 26 is a block diagram of a video processing apparatus 2600. The apparatus 2600 may be used to implement one or more of the methods described herein. The apparatus 2600 may be embodied in a smartphone, tablet, computer, Internet of Things (IoT) receiver, and so on. The apparatus 2600 may include one or more processors 2602, one or more memories 2604 and video processing hardware 2606. The processor(s) 2602 may be configured to implement one or more methods (including, but not limited to, method 2500) described in the present document. The memory (memories) 2604 may be used for storing data and code used for implementing the methods and techniques described herein. The video processing hardware 2606 may be used to implement, in hardware circuitry, some techniques described in the present document.

FIG. 28 is another example of a block diagram of a video processing system in which disclosed techniques may be implemented. FIG. 28 is a block diagram showing an example video processing system 2800 in which various techniques disclosed herein may be implemented. Various implementations may include some or all of the components of the system 2800. The system 2800 may include input 2802 for receiving video content. The video content may be received in a raw or uncompressed format, e.g., 8 or 10 bit multi-component pixel values, or may be in a compressed or encoded format. The input 2802 may represent a network interface, a peripheral bus interface, or a storage interface. Examples of network interface include wired interfaces such as Ethernet, passive optical network (PON), etc. and wireless interfaces such as Wi-Fi or cellular interfaces.

The system 2800 may include a coding component 2804 that may implement the various coding or encoding methods described in the present document. The coding component 2804 may reduce the average bitrate of video from the input 2802 to the output of the coding component 2804 to produce a coded representation of the video. The coding techniques are therefore sometimes called video compression or video transcoding techniques. The output of the coding component 2804 may be either stored, or transmitted via a communication connected, as represented by the component 2806. The stored or communicated bitstream (or coded) representation of the video received at the input 2902 may be used by the component 2808 for generating pixel values or displayable video that is sent to a display interface 2810. The process of generating user-viewable video from the bitstream representation is sometimes called video decompression. Furthermore, while certain video processing operations are referred to as “coding” operations or tools, it will be appreciated that the coding tools or operations are used at an encoder and corresponding decoding tools or operations that reverse the results of the coding will be performed by a decoder.

Examples of a peripheral bus interface or a display interface may include universal serial bus (USB) or high definition multimedia interface (HDMI) or Displayport, and so on. Examples of storage interfaces include SATA (serial advanced technology attachment), PCI, IDE interface, and the like. The techniques described in the present document may be embodied in various electronic devices such as mobile phones, laptops, smartphones or other devices that are capable of performing digital data processing and/or video display.

In some embodiments, the video coding methods may be implemented using an apparatus that is implemented on a hardware platform as described with respect to FIG. 26 or 28.

Various techniques and embodiments may be described using the following clause-based format. These clauses may be implemented as preferred features of some embodiments.

A first set of clauses use some of the techniques described in the previous section, including, for example, items 16-18, 23, and 26 in the previous section.

1. A method for video processing, comprising: determining that a conversion between a current video block of a video and a coded representation of the current video block is based on a non-affine inter AMVR mode; and performing the conversion based on the determining, and wherein the coded representation of the current video block is based on a context based coding, and wherein a context used for coding the current video block is modeled without using an affine AMVR mode information of a neighboring block during the conversion.

2. The method of clause 1, wherein a non-affine inter AMVR mode index of the neighboring block coded is utilized.

3. The method of clause 2, wherein a context index used for coding the non-affine inter AMVR mode index of the current video block is dependent on at least one of an AMVR mode index, an affine mode flag, or an availability of left and above neighboring blocks, the non-affine inter AMVR mode index indicating a certain MVD precision.

4. The method of clause 3, wherein offset values are derived for the left neighboring block and the above neighboring block, respectively, and the context index is derived as the sum of the offset values of the left neighboring block and the above neighboring block.

5. The method of clause 4, wherein at least one of the offset values is derived as 1 in case that a corresponding neighboring block is available and is not coded in an affine mode and the AMVR mode index of the neighboring block is not equal to 0, and the at least one of the offset values is derived as 0 otherwise.

6. The method of clause 1, wherein affine AMVR mode information of the neighboring block is not directly used but indirectly used with a function of the affine AMVR mode information.

7. The method of clause 6, wherein the function returns true in a case that amvr_mode[xNbL][yNbL] or amvr_flag[xNbL][yNbL] of the neighboring block covering (xNbL, yNbL) indicates a certain MVD precision.

8. The method of clause 1, wherein the affine AMVR mode information of the neighboring block is utilized for coding a first syntax element of a non-affine inter AMVR mode of the current video block.

9. The method of clause 1, wherein, in a case that an AMVR mode of the current video block is represented by multiple syntax elements, AMVR mode information of the neighboring block coded in both non-affine inter mode and affine inter mode is utilized for coding any one of the multiple syntax elements.

10. The method of clause 1, wherein, in a case that an AMVR mode of the current video block is represented by multiple syntax elements, AMVR mode information of the neighboring block coded in affine inter mode is not utilized for coding any one of the multiple syntax elements.

11. The method of clause 1, wherein, in a case that an AMVR mode of the current video block is represented by multiple syntax elements, AMVR mode information of the neighboring block coded in affine inter mode is not directly utilized but indirectly used for coding any one of the multiple syntax elements.

12. The method of any of clauses 9-11, wherein, the AMVR mode of the current video block includes affine inter AMVR mode and non-affine inter AMVR mode.

13. A method for video processing, comprising: determining that a conversion between a current video block of a video and a coded representation of the current video block is based on an affine adaptive motion vector resolution (affine AMVR) mode; and performing the conversion based on the determining, and wherein the coded representation of the current video block is based on a context based coding, and wherein a variable controls two probability updating speeds for a context.

14. The method of clause 13, wherein the two probability updating speeds include a faster updating speed defined by (shiftIdx>>2)+2, shiftIdx indicating the variable.

15. The method of clause 13, wherein the two probability updating speeds include a slower updating speed defined by (shiftIdx & 3)+3+shift0, shift0 defined by (shiftIdx>>2)+2 and shiftIdx indicating the variable.

16. The method of clause 14, wherein the faster updating speed is between 2 and 5.

17. A method for video processing, comprising: determining that a conversion between a current video block of a video and a coded representation of the current video block is based on an affine AMVR mode; and performing the conversion based on the determining, and wherein the coded representation of the current video block is based on a context based coding, and wherein a context used for coding the current video block is modeled using a coding information of a neighboring block for which an AMVR mode of both affine inter mode and normal inter mode is used during the conversion.

18. The method of clause 17, wherein AMVR mode information of the neighboring block is directly used for the context based coding.

19. The method of clause 17, wherein AMVR mode information of the neighboring block coded in normal inter mode is disallowed for the context based coding.

20. The method of clause 17, wherein AMVR mode information of the neighboring block coded in normal inter mode is not directly used but indirectly used with a function of the AMVR mode information.

21. The method of clause 17, wherein AMVR mode information of the neighboring block is utilized for coding a first syntax element of the affine AMVR mode of the current video block.

22. The method of clause 17, wherein, in a case that the affine AMVR mode is represented by multiple syntax elements, AMVR mode information of the neighboring block coded in both affine inter mode and normal inter mode is utilized for coding any one of the multiple syntax elements.

23. The method of clause 17, wherein, in a case that the affine AMVR mode is represented by multiple syntax elements, AMVR mode information of the neighboring block coded in normal inter mode is not utilized for coding any one of the multiple syntax elements.

24. The method of clause 17, wherein, in a case that the affine AMVR mode is represented by multiple syntax elements, AMVR mode information of the neighboring block coded in normal inter mode is not directly utilized but indirectly used for coding any one of the multiple syntax elements.

25. A method for video processing, comprising: determining, for a conversion between a current video block of a video and a coded representation of the current video block, a usage of multiple contexts for the conversion; and performing the conversion based on the determining, and wherein the multiple contexts are utilized for coding a syntax element indicating a coarse motion precision.

26. The method of clause 25, wherein the multiple contexts correspond to exactly two contexts.

27. The method of clause 26, wherein the multiple contexts are selected based on whether the current video block is affine coded.

28. The method of clause 25, wherein another syntax element is used to indicate that the conversion is based on an affine AMVR mode.

29. The method of clause 28, wherein the another syntax element is coded with only a first context and the syntax element is coded with only a second context.

30. The method of clause 28, wherein the another syntax element is coded with only a first context and the syntax element is bypass coded.

31. The method of clause 28, wherein the another syntax element is bypass coded and the syntax element is bypass coded.

32. The method of clause 25, wherein all syntax elements related to motion vector precisions are bypass coded.

33. The method of clause 25 or 26, wherein the syntax element indicates a selection from a set including 1-pel or 4-pel precision for the normal inter mode.

34. The method of clause 25 or 26, wherein the syntax element indicates a selection from at least between 1/16-pel or 1-pel precision for the affine mode.

35. The method of clause 34, wherein the syntax element is equal to 0, ⅙-pel precision for the affine mode.

36. The method of clause 34, wherein the syntax element is equal to 1, 1-pel precision for the affine mode.

37. The method of any of clauses 1 to 36, wherein the performing of the conversion includes generating the coded representation from the current video block.

38. The method of any of clauses 1 to 36, wherein the performing of the conversion includes generating the current video block from the coded representation.

39. An apparatus in a video system comprising a processor and a non-transitory memory with instructions thereon, wherein the instructions upon execution by the processor, cause the processor to implement the method in any one of clauses 1 to 38.

40. A computer program product stored on a non-transitory computer readable media, the computer program product including program code for carrying out the method in any one of clauses 1 to 38.

A second set of clauses use some of the techniques described in the previous section, including, for example, items 19-21 and 23 in the previous section.

1. A method of video processing, comprising: making a determination, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use a symmetric motion vector difference (SMVD) mode based on a currently selected best mode for the conversion; and performing the conversion based on the determining.

2. The method of clause 1, wherein the SMVD mode is used without explicit signaling of at least one reference index of reference list.

3. The method of clause 2, wherein the reference index is derived based recursive picture order count (POC) calculation.

4. The method of clause 1, wherein, in a case that the currently selected best mode is a merge mode or a UMVE mode, the determining disables the usage of the SMVD mode.

5. The method of clause 4, wherein the UMVE mode applies a motion vector offset to refine a motion candidate derived from a merge candidate list.

6. The method of clause 1, wherein, in a case that the currently selected best mode is not coded with the SMVD mode, the determining disables the usage of the SMVD mode.

7. The method of clause 1, wherein, in a case that the currently selected best mode is an affine mode, the determining disables the usage of the SMVD mode.

8. The method of clause 1, wherein, in a case that the currently selected best mode is a sub-block merge mode, the determining disables the usage of the SMVD mode.

9. The method of clause 1, wherein, in a case that the currently selected best mode is an affine SMVD mode, the determining disables the usage of the SMVD mode.

10. The method of clause 1, wherein, in a case that the currently selected best mode is an affine merge mode, the determining disables the usage of the SMVD mode.

11. The method of any of clauses 2-10, wherein the determining is applied only when a MVD (motion vector differences) precision is greater than or equal to a precision.

12. The method of any of clauses 2-10, wherein the determining is applied only when a MVD precision is greater than a precision.

13. The method of any of clauses 2-10, wherein the determining is applied only when MVD precision is smaller than or equal to a precision.

14. The method of any of clauses 2-10, wherein the determining is applied only when MVD precision is smaller than a precision.

15. A method for video processing, comprising: making a determining, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use an affine SMVD mode based on a currently selected best mode for the conversion; and performing the conversion based on the determining.

16. The method of clause 15, wherein, in a case that the currently selected best mode is a merge mode or a UMVE mode, the determining disables the usage of the affine SMVD mode.

17. The method of clause 15, wherein, in a case that the currently selected best mode is not coded with the affine SMVD mode, the determining disables the usage of the affine SMVD mode.

18. The method of clause 15, wherein, in a case that the currently selected best mode is a sub-block merge mode, the determining disables the usage of the affine SMVD mode.

19. The method of clause 15, wherein, in a case that the currently selected best mode is an SMVD mode, the determining disables the usage of the affine SMVD mode.

20. The method of clause 15, wherein, in a case that the currently selected best mode is an affine merge mode, the determining disables the usage of the affine SMVD mode.

21. The method of any of clauses 16-20, wherein the determining is applied only when an affine MVD precision is greater than or equal to a precision.

22. The method of any of clauses 16-20, wherein the determining is applied only when an affine MVD precision is greater than a precision.

23. The method of any of clauses 16-20, wherein the determining is applied only when an affine MVD precision is smaller than or equal to a precision.

24. The method of any of clauses 16-20, wherein the determining is applied only when am affine MVD precision is smaller than a precision.

25. The method of clause 1 or 15, further comprising: determining characteristics of the current video block, the characteristics including one or more of: a block size of the video block, a slice or picture or tile type of the video block, or motion information related to the video block, and wherein the determining is also based on the characteristics.

26. The method of any of clauses 1 to 25, wherein the performing of the conversion includes generating the coded representation from the current block.

27. The method of any of clauses 1 to 25, wherein the performing of the conversion includes generating the current block from the coded representation.

28. An apparatus in a video system comprising a processor and a non-transitory memory with instructions thereon, wherein the instructions upon execution by the processor, cause the processor to implement the method in any one of clauses 1 to 27.

29. A computer program product stored on a non-transitory computer readable media, the computer program product including program code for carrying out the method in any one of clauses 1 to 27.

From the foregoing, it will be appreciated that specific embodiments of the presently disclosed technology have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of the invention. Accordingly, the presently disclosed technology is not limited except as by the appended claims.

Implementations of the subject matter and the functional operations described in this patent document can be implemented in various systems, digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Implementations of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible and non-transitory computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them. The term “data processing unit” or “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.

A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

It is intended that the specification, together with the drawings, be considered exemplary only, where exemplary means an example. As used herein, the use of “or” is intended to include “and/or”, unless the context clearly indicates otherwise.

While this patent document contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

Only a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document. 

What is claimed is:
 1. A method of video processing, comprising: making a determination, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use a symmetric motion vector difference (SMVD) mode based on a currently selected best mode for the conversion; and performing the conversion based on the determining.
 2. The method of claim 1, wherein the SMVD mode is used without explicit signaling of at least one reference index of reference list.
 3. The method of claim 2, wherein the reference index is derived based recursive picture order count (POC) calculation.
 4. The method of claim 1, wherein, in a case that the currently selected best mode is a merge mode or a UMVE mode, the determining disables the usage of the SMVD mode.
 5. The method of claim 4, wherein the UMVE mode applies a motion vector offset to refine a motion candidate derived from a merge candidate list.
 6. The method of claim 1, wherein, in a case that the currently selected best mode is not coded with the SMVD mode, the determining disables the usage of the SMVD mode.
 7. The method of claim 1, wherein, in a case that the currently selected best mode is an affine mode, the determining disables the usage of the SMVD mode.
 8. The method of claim 1, wherein, in a case that the currently selected best mode is a sub-block merge mode, the determining disables the usage of the SMVD mode.
 9. The method of claim 1, wherein, in a case that the currently selected best mode is an affine SMVD mode, the determining disables the usage of the SMVD mode.
 10. The method of claim 1, wherein, in a case that the currently selected best mode is an affine merge mode, the determining disables the usage of the SMVD mode.
 11. The method of claim 2, wherein the determining is applied only when a MVD (motion vector differences) precision is greater than or equal to a precision.
 12. The method of claim 2, wherein the determining is applied only when a MVD precision is greater than a precision.
 13. The method of claim 2, wherein the determining is applied only when MVD precision is smaller than or equal to a precision.
 14. The method of claim 2, wherein the determining is applied only when MVD precision is smaller than a precision.
 15. The method of claim 1, wherein, the SMVD mode is an affine SMVD mode.
 16. The method of claim 1, wherein the performing of the conversion includes generating the coded representation from the current block.
 17. The method of claim 1, wherein the performing of the conversion includes generating the current block from the coded representation.
 18. An apparatus for processing video data comprising a processor and a non-transitory memory with instructions thereon, wherein the instructions upon execution by the processor, cause the processor to: make a determination, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use a symmetric motion vector difference (SMVD) mode based on a currently selected best mode for the conversion; and perform the conversion based on the determining.
 19. A non-transitory computer-readable storage media storing instructions that cause a processor to: make a determination, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use a symmetric motion vector difference (SMVD) mode based on a currently selected best mode for the conversion; and perform the conversion based on the determining.
 20. A non-transitory computer-readable recording medium storing a bitstream of a video which is generated by a method performed by a video processing apparatus, wherein the method comprises: making a determination, for a conversion between a current video block of a video and a coded representation of the current video block, whether to use a symmetric motion vector difference (SMVD) mode based on a currently selected best mode for the conversion; and generating the bitstream based on the determining. 